Compilation issue post update to Nim 2.0

Thanks. I am using EndeavourOS latest version. I used "sudo pacman -Syu nim" to update nim application. I tried running nim with "nim --lib:/usr/lib/nim c file.nim" and it works. I did not clearly understood your second comment. I have removed nim completely and then reinstalled but the folder

Improving Examples and Documentation

Absolutely, that's what we should go for. If you want to go minimal, Starlette (FastAPI's little-known base) will do. I do suspect that you have the second part the wrong way around. I think part of why those examples are popular is because they put in the good documentation _first_.

Improving Examples and Documentation

I think the websites of projects like Vue, Flask, FastAPI, or httpx shows the ideal document amount of libraries like karax, jester, etc. When a Nim library is fairly popular, it should be slowly promoted to get as well-documented as those projects.

Improving Examples and Documentation

@cmc Yeh, Can.l is the great person behind owlkettle, all I did was provide the starting point for the nimibook and hook docs.

Improving Examples and Documentation

That is an **incredibly** good point and I completely blanked we had that. I was collecting a bunch of smaller doc changes (you may remember that I tend to do the odd doc PR here or there, most recent one e.g. slight expansion to the testament docs) and **entirely** forgot that button existed.

Improving Examples and Documentation

Arch Linux has the best technical documentation I ever encountered, full of copy/pastable stuff that comes from a comprehensive list of things you might want to do. Then you can add your own stuff from there. Fantastic. The documentation is a wiki! Pretty much like what you're proposing. Of cou

Improving Examples and Documentation

I have to admit that I actually haven't ever used the `Edit` button. However it only halfway solves the problem. You still need a fork on your GitHub, you still need to follow up the PR, and the PR of course still has to get merged. With the live-input system I propose you could just fire away a

Mastering Nim 2.0

I keep looking for alternative distributors but much of them are connected to Amazon in some way or another anyway. If you buy the hardcover version I indeed make more profit but don't worry about that and buy the version that suits you.

Improving Examples and Documentation

> So you're the owlkettle guy? Owlkettle has some really, really nice > documentation!! He isn't. Isofruit/Phil works on mapster, snorlogue, ... While the creator of owlkettle is Can Lehmann

Improving Examples and Documentation

I agree that we don't have to please everybody, especially not everybody on Twitter (yikes!). However- this guy's reaction, strong interest in Nim and then outright disgust at the careless state of the docs closely mirrored my own, so it resonated strongly with me. I was almost that guy- I almos

Improving Examples and Documentation

So you're the owlkettle guy? Owlkettle has some really, really nice documentation!!

Improving Examples and Documentation

I believe the correct way to document such a button would be to have a little blurb: "How to contribute to this guide: Use the edit button to create a standard github pull request. We are mostly looking for contributions in expanded examples, but correcting errors is also welcome." I actually u

Improving Examples and Documentation

This would be absolutely fantastic. I'm _always_ getting my info from the sources and _never_ expanding the readme. This should be put into the subject "Documentation contribution friction" in our to-be-created documentation plan.

Improving Examples and Documentation

Yeah, you're right! That was pretty cool. I have this blog commenting module I made that looks pretty much like the PHP thing, maybe that's worth a shot. It's kinda like a minimal disqus but without an iframe. Docs were really not bad at all with PHP. The language kind of constantly picked at

Improving Examples and Documentation

> Can we form some group/sub-community (in some channel) which solely focuses > on documentation of the ecosystem? That is an excellent idea. I'm in!!! I think that group could formulate a vision for documentation in Nim (lots of ideas in this thread could go in), and then create a series of st

Improving Examples and Documentation

Yes!!! There is a very simple reason why examples are so important: They allow you to operate on inductive logic- deriving a general rule from special cases. Without them, you have to rely on deductive logic- creating your own special cases from a general rule. This is much, much harder. Someo

Improving Examples and Documentation

Yes it does! No it doesn't! Yes it does ;) I think it kinda does imply that. Right now it's kind of like a road sign pointing at a road block. Remember that 10x underestimation assessment of mine? This is one of those areas where you go against your instincts.

Compilation issue post update to Nim 2.0

Try running nim with specifying lib PATH: `nim --lib:/usr/lib/nim ...` . If that works, you or the package maintainer probably overwritten this config option with wrong directory. Check nim's config files for "/usr/lib/nim/lib"; list all active configs with `nim --hints:on` command while in you

Improving Examples and Documentation

I remember spending time on an "Edit" button for the stdlib docs. The button still works. I got like one contribution in total thanks to this button...

Compilation issue post update to Nim 2.0

I am on Linux system and was using nim 1.6.10. I upgraded to Nim 2.0 today. On compiling my nim program I get this Error nim c "ValData_Validation_2023.nim" (in directory: /home/ajayc/Documents/Valuation/Asian/2023/WorkSpace) Error: cannot open '/usr/lib/nim/lib/system.nim' Compilation failed.

Improving Examples and Documentation

Fair, but I still think the vast vast majority of people consume documentation online. So it makes sense to bring the contribution interface there. And of course, the best would be if we could get the library authors themselves to write docs. I try to document mine as well as possible (although

Improving Examples and Documentation

Commenting on docs and modules I really liked about the php (sic) docs back in the day's