NuttX Port

I took your advice, applied the changes and submitted a pull request. CI seems to have passed. Could you please take a look at the contents?

NuttX Port

Glad to help. Yah the `defined(nuttx)` is a good way. I figure if most of the constants are the same, that let's people see the differences.

NuttX Port

Glad to help. Yah the `defined(nuttx)` is a good way. I figure if most of the constants are the same, that let's people see the differences.

Who wants to do a GSoC about FreeCAD? Program in Nim!

Interesting, Solverspace is what CAD sketcher, add-on for Blender, is using:

Who wants to do a GSoC about FreeCAD? Program in Nim!

Coin3d is used for the rendering bit AFAIK. I think Zolko talks about improving the measurement tool within FreeCAD. [Geometric Constrain Solving](https://en.wikipedia.org/wiki/Geometric_constraint_solving) is about finding a solution when you define constraints between geometric elements, such

robots.txt and sitemap for the forum.

I've created a PR for the forum:

working towards a Nim Devroom at FOSDEM 2023 (physical event)

> btw, for those who went, how was it? I was only there at the FreeCAD day at Friday before FOSDEM and to be honest, I think that I made the right choice. The quality wasn't that well. There were no subjects that I am interested in. I don't know why. Maybe indeed it is Rust. But there were no "

robots.txt and sitemap for the forum.

The updated forums branch please note that this branch also contains my argon2 changes (so that i can run and test it on windows), i would create a fresh branch with only these sitemap changes if you like the general idea.

robots.txt and sitemap for the forum.

Here is a paper from google about sitemaps:

robots.txt and sitemap for the forum.

I've looked through the forums routes, there is one that also allows the name of the post in the url: /t/123/foo Run i think the sitemap should also contains those, i've the feeling that this is even more searchengine friendly.

robots.txt and sitemap for the forum.

I think it would be beneficial for external search engines if the forum would create a sitemap of all posts. The robots.txt could contain an entry for the sitemap that shows search engines the way: Sitemap: https://forum.nim-lang.org/sitemap.xml Run For the sitemap ge

working towards a Nim Devroom at FOSDEM 2023 (physical event)

For me the most interesting part was the "rise" of Rust. It wasn't only, that it was just everywhere, it was also the quality of the talks better than on other trails.

Fast Start Keto Gummies

Fast Start Keto Gummies is a clever dietary enhancement created to support weight reduction. This clinically-demonstrated combination was intended to help people in their quest for wellbeing and health.A solid weight prepares for bones, muscles, the cerebrum, and the heart, among others, to assu

Who wants to do a GSoC about FreeCAD? Program in Nim!

Did you reply at FreeCAD? I am curious.

Who wants to do a GSoC about FreeCAD? Program in Nim!

> I think Coin3d bindings would be needed. TBH I don't know Coin3d enough to answer that question. But if it does than we need to write a wrapper. > It would be interesting to have a Geometric Constrain Solver in Nim too. The > low hanging fruit could be some bindings to Solvespace's constrain

Trouble with Nim debugging in VS Code

Agreed. The debugging situation is not great and a large part of the whole poor tooling situation. Out of curiosity, C++ does name mangling too IIRC? How is that handled by gdb? Is it possible to map the non-mangled symbols in the DWARF data?

Immutable pointer type?

thank you all for your suggestions! The distinct ptr type is a good idea, and view types are mighty interesting. I'll give both a shot

Trouble with Nim debugging in VS Code

This, after NimSuggest/intellisense is the biggest issue on Nim's tooling turning people away. Not sure where the fix would go TBH. Does it require the compiler to do something additional on the emitted symbols? Maybe to dont mangle or remap them to something the debugger can understand if in de

NuttX Port

Thank you for your reply. > You might consider using the posix_other.nim rather than a full copy of the > posix like > lib/posix/posix_nuttx_consts.nim unless there's a lot of > differences. It's a bit of preference. I took a diff and found the following differences in the example.