ivov_dev

6 ms·

1. 1.▲
   by ivov_dev 5mo ago

   Thanks for trying it out! Variant qualification is a name resolution requirement - Lis follows Rust's scoping model where variants are namespaced under the enum. The implementation correctly infers the type, as shown e.g. in the hint `
2. 2.▲
   by ivov_dev 6mo ago

   Thanks for asking! The core of the compiler should be close to 50k LoC, with most of the rest being tests. The project is much older than git history suggests - I started a fresh repository for the initial release after several months of ex
3. 3.▲
   by ivov_dev 6mo ago

   You are right, and thank you for pointing this out. I've opened an issue: https://github.com/ivov/lisette/issues/12 I have a few approaches in mind and will be addressing this soon.
4. 4.▲
   by ivov_dev 6mo ago

   Thanks for your kind words :) The CLI command `lis run` supports a `--debug` flag to insert `//line source.lis:21:5` directives into the generated Go, so stack traces from runtime errors point back to the original Lisette source p
5. 5.▲
   by ivov_dev 6mo ago

   Support for Go third-party packages is not part of this first release, but the tooling to generate bindings for Go packages (which enables imports from the Go stdlib) is already in place[1]. Extending it to support third-party packages is o
6. 6.▲
   Show HN: Nodemaker, automatic node generator for n8n

   5 points by ivov_dev 6y ago|0 comments
7. 7.▲
   by ivov_dev 6y ago

   Thank you for your writings! Your "Learn in Public" gist inspired me to do so: https://ivov.dev/