zigler

claude and codex are pretty quick to figure out "oh that's not a thing anymore" and figure out what they need to do? i did a 0.15 -> 0.16 port of this library and most of it the LLM did https://github.com/E-xyza/zigler

this was the general motivation for my project zigler: https://github.com/E-xyza/zigler

Zigler! https://github.com/E-xyza/zigler

Bun is an executable as far as I understand. Would it be possible to call Bun directly from another language with bindings? For example Erlang (and Elixir) has Native Implemented Functions[0] (NIF) where you can call native code directly from Erlang. Elixir has the zigler[1] project where you can call Zig code directly from Elixir. Maybe you can see where I'm going with this, but it would be super cool to have the ability to call Javascript code from within Elixir. Especially when it comes to code that should be called on the server and client. I'm the developer of LiveSvelte[2] where we use Node to do SSR but it's quite slow atm, and would be very cool to use Bun for something like this. In any case Bun is super impressive, keep it up! [0] https://www.erlang.org/doc/tutorial/nif.html [1] https://github.com/E-xyza/zigler [2] https://githu

There's also Zigler, that makes writing NIFs in Zig a breeze: https://github.com/E-xyza/zigler

I admit for a long time this was my primary motivation to learn Rust, but, sadly, I haven't come across problems in years that were CPU bound/where I needed something like Rust... Rustler still looks like a great fit if needed, but, depending on the use case, if I were CPU bound and needed to write my own code/not just use a Rust library, I'd be as or more likely to look at using Zig and Zigler[0], for much faster learning curve, and from what I've read, easier tighter integration into elixir, including I think language server integration. Some discussion here[1] though I forget if I listened to this one or not. [0]https://github.com/ityonemo/zigler [1]https://podcast.thinkingelixir.com/83

That looks great, it's a pet peeve of mine that it's difficult to format languages that are encased in another language. Most (all?) editors are only expecting a single "language" in a file. You have a js file? Must contain only JavaScript! Unrelated to 1.13 but thanks to the release notes, I now know about Zigler; which looks really neat. https://github.com/ityonemo/zigler

A few protips for nimble_parsec: - ninja in a struct for your context, just generally a better choice due to the stronger typing. - decide if your parser is a transformer or an analyzer. If it only analyzes text, then throw away all of the text after you use it and use the text stream as a contextual buffer. If it transforms, be consistent about the tokens you return in the stream. Use structs if you can. - build intermediate defparsecs which create testable functions that you can test. If you like, fence them in `if Mix.env == :test` blocks to keep them from being compiled except in test. Example: https://github.com/ityonemo/zigler/blob/master/lib/zig/parse...

challenge accepted: https://github.com/ityonemo/zigler/issues/240

Not an antipattern for nimble_parsec: https://github.com/ityonemo/zigler/blob/fe845a9fbbfef92da8ab... Plus think of how much easier that pipe makes it for you to understand what is going on.

No separation between header and code, structs are better than records (because they bear their data labels when you inspect them, even if you send to another node that doesn't recognize them), and also since elixir requires that the tags are modules, you can use them for polymorphism (this is the best of OOP without OOP). Much better documentation support, better compile time infrastructure, smart metaprogramming (this package would be a PITA in erlang: https://github.com/ityonemo/zigler), opinionated but optional directory organization. Module namespaces which are trivially subdivided and aliased, easier time making anonymous GenServers. The Task module, full stop. The registry module, as well.

Normally I would agree for webapps but in this case, it's for generating low-level code. In general, It's only a mistake if it's burdensome. I only have about 30 of these tests, and they are for critical code (I want the end user to be able to review the test and be confident that the generated code doesn't contain memory leaks, etc). https://github.com/ityonemo/zigler/blob/3de4d6fe4def265b689b...

You can also write Elixir/BEAM NIF extensions in Nim and Zig as well using Nimler or Zigler, resp [1,2]. Also I’ve found writing native extensions for the BEAM is simpler than many other dynamic languages since it relies on immutable data. It’s roughly the same as just a function to deserialize/serialize data with some extra references to GC’ed data. Especially with dirty “NIF”s (they allow the functions to run for as long as they want without messing up the BEAM scheduler). 1: https://github.com/wltsmrz/nimler 2: https://github.com/ityonemo/zigler