I haven't spent a lot of time in the guts of the compiler, but from what I've
seen it's in good shape. Nim is evolving quickly (I can't think of a mature
language that's moving faster), is fairly easy to work on, and critical bugs
are fixed quickly when found. I'm sure there are things the team
During my years lurking in the Nim community, I've got the impression that the
Nim compiler has evolved a lot during the years but sadly hasn't been
refactored when new big changes have been made, but instead they were added on
top of the old framework. And this fact of adding ad-hoc solutions u
@PMunch Yes generics or overloads are supported, you got to define a concreate
type or proc in the bindings DSL (otherwise how languages like C which don't
support them work?):
generics:
exportSeq seq[float32]:
discard
exportSeq seq[Span]:
discard
IMHO, commas are the semicolons of Nim/Python. If statements can be separated
with a line break, why not other things? It's annoying in situations like this:
const nested = {
"things": [
"foo",
"bar",
],
"stuff": [
"baz",
"quux",
Maybe is possible, but I do not know if worth it, for stability in the long
run, I would only change syntax for Pattern Matching, but other than that I
would leave as it is...
Hey! Currently in Nim the "command" syntax is one of the only cases in which
trailing commas are not allowed.
foo 10,
20,
30,
# Error: invalid indentation
Run
I was wondering if this could be lifted in the future, or if there's a reason
for it (di
So what I want is not necessarily the mere existence of a distinct string path
type, which i could create myself very easily, but rather for that type to be
used consistently throughout the standard library wherever paths are used, such
that the standard way to deal with paths is through the sin
I haven't seen this before, thanks for pointing me to it. I'll have a look at
it, but if this is what I think it is, then it is a first step in the direction
that I propose. See my previous comment reacting to @demotomohiro for a fuller
exposition of the intent and scope of the changes i am prop
