Spec - core concepts

[haxscramper]

• [ ] Core language concepts
  • [x] expression
  • [x] statement
  • [ ] errors
  • [ ] type inference
  • [ ] resolution, dispatch, and overloads
  • [ ] module resolution
  • [ ] type tagging, untagging, and comparison
  • [ ] differences between backends
  • [ ] core defines and the environment
  • [ ] compile time
  • [ ] side effect
  • [ ] typed and untyped macros - this one is tricky, but the whole concept of semantic analysis is not something an average user probably familiar with, so it warrants special attention.
  • [ ] variables, scopes, assignments (to a single variable, to multiple variables, how many times an expression for a multivar assign is evaluated?)
  • [ ] destructors, sinks, moves? I'm not sure which part of the specification it belongs to - procedures (because of sink arguments), regular variables, scoping, something else? How {.global.} destructor is handled btw
  • [ ] literals - preferably tests should include a solution that would also test things separately from the lexer, in a way that would allow specification to ensure changes to the lexer don't propagate bugs. Something like int(2f) == 2, for i in 0 .. 2: inc tmp; tmp == 2, 1 + 1 == 2 etc.
• [ ] Core compilation concepts
  • [ ] Project file/module
  • [ ] Package (not much more than a directory with a nim file/module(s))
• [ ] Basic control flow constructs
  • [ ] while + continue/break
  • [ ] while statement scoping
  • [ ] if
  • [x] Using as a statement
  • [x] Using as expression
  • [ ] if statement scoping
  • [ ] case
  • [x] Case expressions
  • [ ] Allowed types of variables to be used
  • [x] Case for strings
  • [ ] Case for enums, enum sets, enum ranges
  • [ ] else, elif branches for case statements
  • [x] Using case as an expression
  • [ ] of branch variable scoping
  • [ ] block
  • [ ] break to labeled block
  • [ ] break to block
  • [ ] block variable scoping
  • [ ] try/catch/finally (with and without user-defined exceptions)
  • [ ] Try expression
  • [ ] finally in contexts different from simple exception
  • [ ] Control flow transfer between procedure calls

[saem]

Added compilation concepts, this is going to be a bit subtle, because we'll likely want to layer then out too. So for example, resolution of paths vs import names is core, but specifying flags on the CLI or whatever might be complier CLI specification and/or doesn't strictly need to be followed.

Same teasing apart for cfg and nims

[alaviss]

An unsorted list of things to be covered wrt primitive types and literals:

• [ ] intX:
  • [ ] Conversion relation with other sized int
  • [ ] Conversion relation with unsigned int
  • [ ] Conversion relation with floating points
• [ ] floatX:
  • [ ] Conversion relation with other floating point sizes
  • [ ] Conversion relation with intX
  • [ ] Conversion relation with unsigned integers