custom pragmas are not supported for enum fields

Not quite sure what you're trying to do, but you are aware you can change the value Nim enums serialize to like this right? type MajorType* = enum mtPositiveInteger = 0 mtNegativeInteger = 1 mtBinaryString = 2 mtUnicodeString = 3

creating nimstring using pre-allocated buffer to prevent copy

This isn't exactly what you're asking for, but if you just want something with a fixed size or capacity that is resistant to copying issues and heap-related bugs, I wrote a library called [stack_strings](https://github.com/termermc/nim-stack-strings) that has a fixed-sized stack-allocated buffe

NIR

Now I get the context. Thank you!

nlvm 1.6.16 - now with a REPL

Just a friendly reminder for everyone who would try this on *nix systems: You can get command history and left/right arrow navigation with `rlwrap`: $ rlwrap nlvm r Run

custom pragmas are not supported for enum fields

I feel like this should be allowed. I'm rewriting some two year old code and wanted to move from an external code generator to using a macro. However, I can't tag the proper serialization values on to the enums due to this restriction. template id_key(value: int) {.pragma.}

related_post_gen benchmark

I've continued to tinker with the `nim` and `nim_con` implementations, trying some changes based on the D and Go impls, etc. Sometimes it works out and Nim moves up in the rankings. However, I'm run into a problem and am unsure how to proceed. If anyone has any ideas...

nlvm 1.6.16 - now with a REPL

Latest nlvm somewhat unusually comes with a new feature - a REPL based on the already present JIT support. With the REPL / JIT, you can now run Nim code compiled to native CPU instructions without creating binaries - incrementally or from files. The feature puts together a lot of infrastructure

nim not finding cross-compiler in PATH on Win10

I've found a clue to this puzzle, but still can't find a solution. When I compile with my cross-compile arguments on the command line, I get a different result than if I compile with the cross-compiler .exe as the only command line argument and the remaining cross-compile args in the `nim.cfg`.

Science behind Active Keto Gummies Australia

Active Keto Gummies Australia:- These Vitamin Dee Gummies Australia are incredibly portable and easy to consume. This makes them a fantastic option for individuals with busy lifestyles, allowing you to stay on track with your dietary goals even when you're not at home. Facebook Page:-

avr_io - nim register bindings and utilities for AVR microcontrollers

Well currently the design is board-oriented. But I think it should maybe have another level of abstraction in-between to make it easier to define boards using the same microcontroller. I was primarily looking at the USART, MappedIO, and interrupts, but of course adding the list of chips would b

avr_io - nim register bindings and utilities for AVR microcontrollers

Hi, I did not know about that, it seems like a wonderful project I will for sure take a look at it in more detail! Am i right in understanding it is geared towards programming on let's say, boards more than specific microcontrollers in general? What were you interested in, that it's implemented

NIR

> I did not find a roadmap 2024. Does a roadmap for 2024 exist already? Sorry, no, I'm still writing it.

NIR

IC is incremental compilation.

NIR

As an outsider (who had used Nim for a little while and possibly wants to get back into it): What is **IC**?