Yorick Peterse
Yorick Peterse
Kotlin has a somewhat similar feature to the `let` method described above: https://kotlinlang.org/docs/scope-functions.html#let
Come to think of it: since Djot is mostly compatible with Markdown, I think it _should_ be fine to use Djot instead of Markdown; at least Djot should be easier...
@spartanatreyu My plan is to do the exact opposite :smile:: No configuration settings whatsoever (e.g. like gofmt), and use 2 spaces for indentation like we do now. The moment you...
Regarding markup: I looked into Djot, but it's equally annoying to parse. I started working on a Markdown-like language at https://github.com/yorickpeterse/inko-markdown/tree/parser. I'm aiming to keep it as close as possible...
@spartanatreyu The goal of Inko's code formatter is to enforce a single style across all Inko projects. Enforcing the style preferences of a specific project is specifically a non-goal, and...
For syntax highlighting: My personal website uses the following languages for code snippets: - bash - fish - inko - make - perl - ruby - rust - toml The...
[inko-syntax](https://github.com/yorickpeterse/inko-syntax) now supports the necessary languages. The setup as a whole could be improved a lot, but it's good enough for our static site generation needs. The next step is...
With https://github.com/yorickpeterse/inko-wobsite released and in use for [my personal website](https://github.com/yorickpeterse/yorickpeterse.com), this can be closed. In the coming weeks I'll start porting the Inko website to inko-wobsite. I'd also like to...
The [inko-doc](https://github.com/inko-lang/inko/tree/inko-doc) branch now contains the necessary changes to produce a bunch of JSON files containing documentation information. Rather than including a static site generator (amongst other things) directly in...
https://github.com/inko-lang/inko/issues/664 is taken care of. The next step is to upgrade the following packages to be compatible with Inko 0.15.0, such that we can use them to build the documentation...