Nim v2: what would you change?

> It's a productivity killer to remember that for arguments of type arg2: > MyEnum you need to use 'ml' prefix for this enums like mlOpt1, mlOpt2, etc. > It also reduces discoverability as nimsuggest doesn't autocomplete either > MyEnum.Opt1 nor by manually triggering foobar(arg2: . I'm not > s

Nim v2: what would you change?

If the v2 will make the --mm:arc --mm:orc --threads:on default, then make them works well all, include task, channle, isolate, threadpool, locks, async, etc.

Nim v2: what would you change?

There's a few breaking changes that come to my mind, though mostly limited to suggestions solving issues which have required me to change programming architectures or idioms to work around. These items make writing certain kinds of software, especially system software, more difficult: * Prov

Nim v2: what would you change?

The biggest thing for me would be locking in --threads:on and --mm:arc or--mm:orc when compiling Nim + hooks working really well with these default compiler settings. Right now it feels like the moment I want to write something using hooks (eg `=destroy`) or that needs threading I am basically

Nim v2: what would you change?

Well, just to add my point to the wish list: unconstrained recursive module imports

Nim v2: what would you change?

I hope the stdlib could be updated for `sink` parameters. Many procs (like `&` for string) don't have to consume their arguments, but it would be more efficient if they do. Their arguments are seldomly used after the call.

Nim v2: what would you change?

Most of the time i will be the anti-breakage voice. I really hope v2 doesn't become a dogpile of everyone's favorite breaking change (and i trust it won't, since thankfully the changes aren't up to democratic vote). Every breaking change is a cost incurred on those who have already invested in t

Nim v2: what would you change?

Personally what I'd appreciate to see with 2.0 is an increase in code reuse using concepts and openarrays. Also more encouragement of using distincts. For instance a lot of the `strutils` module isnt specialized for `string` but could be specialized for `openArray[char]` or just a concept. For i

Nim v2: what would you change?

Some ideas: Change object initialization syntax to use `=` instead of `:`, to be consistent with the rest of the language. let x = Complex(re = -1, im = 1) Run Maybe make `object` syntactic sugar for `distinct tuple` instead of a separate concept? Does this make sens

Nim v2: what would you change?

> Even tooling can't be made better because it all relies on the compiler - > e.g. nimsuggest, nim check, etc. While you're at it, can we get rid of all globals in compiler and make it an object, so it can be compiled as a dynamic library and instantiated / destroyed at will ?

Nim v2: what would you change?

More batteries included: Microsoft Excel became a popular programming environment in finance and trading (despite being Excel) mostly because it provided spreadsheet+charting+programming in one relatively monolithic and stable package. Distributing a set of libraries together with the compiler

Nim v2: what would you change?

Personally, to me changes to the language seem far less important than (1) fixing as many bugs as possible and (2) finishing work on all the initiatives already partially implemented: view types, user-defined defaults and init hooks, polishing new threading primitives and building upon them. Th

Nim v2: what would you change?

and adopting `init/new(typedesc)`

Nim v2: what would you change?

What you describe seems right. At first I thought, static was a way to call a proc that would be evaluated at compile time, precomputing the result. Sort of an extension to const, but without creating explicit constants. Think when you need to have 1/2 as a Fraction.

Nim v2: what would you change?

Not sure what you mean, and frankly I don't know how `static` works internally, but `static` arguments are just generics in a different form.

Nim v2: what would you change?

Remove static, improve the compiler to a point it's no longer needed, for me it's very weird that a static proc parameter is creating an instantiation for every value passed to it. Is a static value a type? Is there any performance increase for operating this way?

Nim v2: what would you change?

I would also like using tabs for indentation without the `#? replace(sub = "\t", by = " ")` first-line-stunt. I agree, that mixing tabs and spaces (like Python allows) is bad, but using solely one kind of indentation character in the whole file should be allowed. I don't want to go into a discu

Nim v2: what would you change?

newSeq() and newString() named inconsistently:

Nim v2: what would you change?

Introduction of existential types, e.g. on the module level.

Nim v2: what would you change?

> If we were to talk about v2 changes, I hope the compiler will finally see > some work on refactoring and making it more accessible to other developers. That's something that can always happen without breakage. Let's focus on language/stdlib changes that _need_ breakage :) > And please, please

Nim v2: what would you change?

As I commented on the thread, it would be great to improve compiler errors

Nim v2: what would you change?

If we were to talk about v2 changes, I hope the compiler will finally see some work on refactoring and making it more accessible to other developers. There's a hard Nim fork called Nimskull (yes, yes, "forbidden" word, I know :P) that has some good ideas, but I don't agree with their radical sol

Nim v2: what would you change?

Please leave style insensitivity alone, this is not in any way, an "ambitious" change. Btw did you know you can send an email to user.n...@gmail.com with a point anywhere between username and it would still work?

Nim v2: what would you change?

Hello all, I have been thinking about Nim v2 lately and after speaking with @Araq about it I think we can be a lot more ambitious with what we change for this major release. The original plan is to change the default GC, but we can do much more (time permitting of course). I wanted to create t