Weird bug(?) with JS backend

Whoa! Thanks a lot for the detailed explanation! :)

cannot open file: db_connector/db_sqlite

If you're using `nimble` to run/build your project, you also have to add all packages it depends on into "requires" in the .nimble file.

asyncdispatch on RTOS(Flat Memory)

I have built the command as an ELF binary and verified that it can be run from external storage (still a simple C command that outputs "hello world"). I will experiment with the possibility of using multiple global dispatchers by splitting the program I create in Nim into separate binaries.

cannot open file: db_connector/db_sqlite

That package doesn't exist, I assume you mean `db_connector`. kryten git:(master) ✗ nimble install db_connectors Prompt: db_connectors not found in any local packages.json, check internet for updated packages? [y/N] Y Answer: Downloading Official package list

cannot open file: db_connector/db_sqlite

Try `nimble install db_connectors`

cannot open file: db_connector/db_sqlite

I'm having trouble running a basic SQLite command in a brand new Nim 2.0.2 project. kryten git:(master) ✗ nim -v Nim Compiler Version 2.0.2 [Linux: amd64] Compiled at 2023-12-15 kryten git:(master) ✗ nimble run --verbose Info: Nimble data file "/home/sergio

cannot open file: db_connector/db_sqlite

Maybe it's the nimble file? Is there a dependency on db_connector in it? If not then that might be the error, since nimble isn't telling nim to include db_connector.

Show Nim: Curly, an efficient thread-ready parallel HTTP client

Puppy's origin story is "I want to make easy cross-platform HTTP requests without -d:ssl and without extra stuff on Windows". Not really server-focused but it certainly works there. Curly's origin story is "my server needs a good way to do lots of low-latency HTTPS RPC calls". This was a harder

About the Nim official documentation update.

Hello. Yes, it is no problem. But I will do it when I am more advanced. Best regards. Antonio F.S.

About the Nim official documentation update.

Hello. As a possible idea, it could be written on Nim's blog. I think it is an important enough issue to be clearly reflected every time it occurs. Best regards. Antonio F.S.

Show Nim: Curly, an efficient thread-ready parallel HTTP client

This is amazing work as always! Not sure if you've documented this elsewhere, but what is the difference between curly and ? Is curly more intended for use on servers (running Linux), or does it work on Windows as well with the libcurl dll? Is it possible to i

About the Nim official documentation update.

Could you post a link to your website? It might be useful for others (me!).

About the Nim official documentation update.

Nothing beats `git log -p doc/grammar.txt` I'm afraid.

TCC on ARM(el) backend problem

Og VS O0

About the Nim official documentation update.

Hello. As I am studying Nim, I am also creating documentation in Spanish on my website. I find that the life of Nim is very active in terms of new capabilities or perhaps also updating and deprecating existing ones. My question is: how to know about this in the official documentation, if Nim g

TCC on ARM(el) backend problem

I am one of the successful users and can also confirm I'd be alienated. :-) :-) :-) { Though I could probably also patch around things. } Not that I think Araq does not know this, but it bears re-mention every time that it's always better to construct something reproducible -- whenever talking

TCC on ARM(el) backend problem

But many use it successfully despite my warnings, removing it would only alienate these users.

Dynamic Typing in Nim

Remember friends don't let friends ask a LLM solve the halting problem on the off chance Skynet frowns upon it.

TCC on ARM(el) backend problem

in fairness to OP it can be often vague where "official support" begins and ends in the compiler. if you don't want people using TCC as the backend then it should be deprecated, otherwise it will be just assumed as a feature, esp. without any experimental flags blocking usage

Dynamic Typing in Nim

I think there's lots of confusion of how the problem is formulated. This whole thing - "static vs dynamic typing" is confusing itself. It should be restated as "if correctness of program validated instantly by the compiler or not". Current compilers can't do that for some class of programs (what

Dynamic Typing in Nim

Language models can’t validate anything, only speculate about it.

TCC on ARM(el) backend problem

> There I only can surrender. codegen on other compilers for atomic compare-and-swap uses the compiler intrinsic directly. TCC being so barebones as it is uses x86 inline asm in absence of compiler builtins. seems like the impl was borrowed [from here.](https://stackoverflow.com/q/833122) ARM

TCC on ARM(el) backend problem

TCC is not officially supported and yes, even for bigger programs the build times with clang are really good.

TCC on ARM(el) backend problem

You're joking? Who says I always want to build Hello-Word-oneliners? And TCC is mentioned in Nim's config and therefore I expect using it being a "legal" idea.