Thoughts on error vs fatal log levels?

If your program has no choice at all but to exit, use fatal If your program can recover in some way from the error, use error

Man pages?

I like nim, but noticed that the docs are in HTML/RST. I tried manually converting them using rst2man or pandoc but they were horrible. Any people who have written a nice conversion script to get man page formats?

Tracking down SIGSEGV. What's the difference between this Nim and C code?

you got it! * 1.7.1 devel 9888a29c3de09c73202b2a955e09e2a7b5e56ea4: SIGSEGV * 1.6.2: SIGSEGV * 1.6.0: OK * 1.4.8: OK * 1.2.0: OK * 1.0.0: OK actually I did try this before, but I forgot to clean the cache after switching with choosenim

Thoughts on error vs fatal log levels?

I am probably over thinking this but I can't seem to make up my mind on which situations call for one or the other. An example would be a program that reads from a file and then does something with that data. If the file does not exist, the program logs a "file not found" message and exits. Woul

Tracking down SIGSEGV. What's the difference between this Nim and C code?

Can you check if your code works on 1.6.0? Because if you're using 1.6.2 you may have hit a regression -

Introducing taskpools, a small lightweight ARC/ORC threadpool

Brilliant! I'm literally just looking into how to do an event/thread pool type of problem in embedded (Zephyr in this case). The sync/spawn types are pretty nice syntax and much better than easier to use than the system built-in work queues. I don't want to run ORC, so this might work nicely. Th

Tracking down SIGSEGV. What's the difference between this Nim and C code?

I've been scratching my head solving a SIGSEGV on my machine when using futhark. I've reduced the problem to a self contained Nim and C files with no external nim packages involved, just plain C linkage. The C program compiles and runs correctly, the Nim program goes SIGSEGV while calling C fun

Introducing taskpools, a small lightweight ARC/ORC threadpool

@Araq, sure you can use whatever style. If readability is a problem you can also change fonts ;). @elcritch, it works with plain-old-data (no need for arc) and any GC that is not thread-local (i.e. memory can be reclaimed from any thread), so malloc/Boehm/ARC/ORC would work.

Non unique / double keys in json

Thanx all. at araq. parsejson.nim interesting but learning-curve. Maybe dig into it at a later time.. at treeform. you probably have a nice replacement for json.nim but now i have finally learned the api of json.nim so i will keep it with that.