Is there way to change «proc» naming?

Terrifying me as hell I even doesn't know which one the most, _proc_ or redundant visual noise in c/cpp **;** Is there some hack to change proc to def or func or fn ? My guess it wouldn't be so difficult to create a fork with just one word for change, and compile it, am i right ?

Re: Are the docs wrong, or is there a compiler bug?

For reference, some more discussion about this here: [https://github.com/nim-lang/Nim/issues/11058](https://github.com/nim-lang/Nim/issues/11058) And quoting @Araq from my conversation with him directly: > it's 'type' for type sections, 'typeof' for typeof and 'typedesc' as the > metatype for

Re: Sielo with Nim

Just a quick reply here to bring this to the frontpage again. :-)

Re: Need help with creating a module featuring asynchronous access of Redis

> Why is this a problem? The procedure does async operations, so it must return > a future. You can hack around and not do that, but then your procedure > becomes blocking. It is a problem because I don't know how to work around that effectively and use these procs as I intend to, i.e. use

Re: Nim vs D

> On the other hand there were Java and Python frontends on the GCC, and where > are they now? I think only Ada and Fortran frontends are really good GCC > citizens along side with C/C++/ObjC. The main Modula-2 developer said at a 2016 GCC development conference that the developers' penchant

Re: Nim vs D

Yeah, honestly I don't see this helping D's popularity all that much. It certainly doesn't hurt, but let's not panic or make it our goal to do the same. The most impactful way to increase Nim's popularity is to _write about it_ and _talk about it_ at conferences and with colleagues and friends.

Re: Need help with creating a module featuring asynchronous access of Redis

Whoa. That's a surprising reaction. I think you might be missing something significant about how async works to think that. > Sadly, your example does not work for me, even with tweaks, as the most > important part proc newMyState cannot work, as it couldn't be able to return > anything else

Re: Nim vs D

Yes, but the DMD's fronend version in GCC 9.1 is like 8 versions behind the current one, this is kinda bad. On the other hand there were Java and Python frontends on the GCC, and where are they now? I think only Ada and Fortran frontends are really good GCC citizens along side with C/C++/ObjC.