Give your model this link
faberlang.dev- Version
- 1.19.1
- Platforms
- macOS arm64 · Linux x64
- License
- MIT OR Apache-2.0
Faber Romanus is written by models, so you install it by handing your model a link. To do it yourself instead, see Without a model.
faber command.faber check on it.All of this happens on your own machine, and your model tells you when the check passes.
Once the check passes, talk to your model the way you would to a colleague. Each prompt below has a copy button.
Write a program and have it explained:
Write a small Faber program that prints the first ten square numbers. Check it with faber check, run it with faber run, then explain each line to me.Bring in code you already have:
Here is a function I already have: <paste it here>. Translate it into Faber, check it, then build it for Rust with faber build -t rust and tell me what changed.Read it in another language:
Make a copy of the hello program spelled in Thai with faber convert --to th-TH. Check the copy, then show me both versions side by side.See what a compiler error says:
Break the hello program on purpose by giving a value the wrong type. Run faber check, read me the diagnostic, and use faber explain on its code so I can see what it means.You can also install and run Faber yourself. Release builds exist for macOS
on Apple silicon and Linux on x86-64. The installer downloads the release for
your machine, checks its checksum, and puts faber in ~/.faber/bin:
curl -fsSL https://raw.githubusercontent.com/faberlang/faber/main/install.sh | sh
export PATH="$HOME/.faber/bin:$PATH"
faber --versionAdd the export line to your shell profile to keep faber on your PATH.
Then write a program, check it, and run it:
printf 'main {\n print "Hello, world!"\n}\n' > hello.fab
faber check hello.fab
faber run hello.fabfaber run prints Hello, world!. To see the same program in another
language, print it to the terminal with faber emit:
faber emit --target go hello.fab
faber emit --target ts hello.fabfaber build -t rust hello.fab builds a Cargo package, so it needs Cargo and
a current stable Rust toolchain (rustup update). The
cheat sheet shows how Faber is written, one topic per page,
and faber explain <code> explains any diagnostic the compiler prints.
You do not need to write Faber to read it. These pages show what your model writes and why it looks the way it does.
faber commands, one page per topic.