Missing features for Nim 3

[Araq]

This issue tracks what is missing before we can declare Nimony to be feature complete for Nim 3.

• field setters aka proc field=
• Implicit generics
• First class iterators
• Effect tracking
• Heap based exceptions
• Macros
• () and . overloading
• Style insensitivity
• ORC's cycle collector

Note we first should focus on making the features we have stable rather than adding even more.

[ASVIEST]

I wouldn’t say that case sensitivity is a good thing.
Case insensitivity lets a camelCase program interact with snake_case libraries, and it also prevents having two identifiers like V4L2_BAD_NAME and V4L2_BAD_nAME.
(I don’t remember the exact details anymore, but in v4l2 there was some terribly named item that differed from another only by letter case.)

Usually this prevents errors, but sometimes you end up with something like
gameStop and
gamesTop,
and that can be annoying.

However, there were proposals for improving the case-insensitivity mechanism in nim-lang/RFCs#547

Additionally, you could add a pragma to make a module case sensitive.

[Araq]

I corrected my typo. Sorry about the confusion.

[nocturn9x]

I wouldn’t say that case sensitivity is a good thing. Case insensitivity lets a camelCase program interact with snake_case libraries, and it also prevents having two identifiers like V4L2_BAD_NAME and V4L2_BAD_nAME. (I don’t remember the exact details anymore, but in v4l2 there was some terribly named item that differed from another only by letter case.)

Usually this prevents errors, but sometimes you end up with something like gameStop and gamesTop, and that can be annoying.

However, there were proposals for improving the case-insensitivity mechanism in nim-lang/RFCs#547

Additionally, you could add a pragma to make a module case sensitive.

I would say case insensitivity, while being mostly harmless, is probably one of the silliest features of nim (personally I never used the feature unless I made a typo, and it bothered me greatly that it wasn't an error, but maybe that's just me). I say we lose it.

Also @Araq I am extremely happy to see you addressing basically all of my current pain points with nim 2 with nimony (the generics especially). As someone who has been writing a LOT of nim lately, I will watch nimony's development very closely!