This is a living document - delete things when done. Avoid discussion.
Current version (Cataract Creek)
+- functions to return type with 'use'
+- functions to return structure with name assignment - bare 'use'?
+- '?' prefix operator returns Boolean
+- reference to struct (@foo), with @new, @free, @nil
+- more number types, no units yet
+
+Later
+- string manipulation
+- file i/o
+- enum
+- basic methods
- structs
- const fields ... what does that mean? Assign once as initialization?
Can be used for array size? What else?
- anonymous field - array or struct (or pointer to these)
multiple anon struct are allowed if they don't conflict
- - [] can apply to anon array field
- - anon struct field gets fields interpolated
+ no - transparent fields! They still have a name, but you can
+ look through it.
+ - [] can apply to transparent array field
+ - transparent struct field gets fields interpolated
- - anon fields have no name before the :, so
+ - How to give attributes? just say the word?
struct foobar:
- :content
+ x:content transparent
size:number
- manifest values for arrays and structs [a,b,c]
That last doesn't parse easily, unless we require tags... not a good idea.
[ .[1] = a, .[2] = b ] ?? Maybe.
or () to group, [] for index. To (.foo=a) ( [1] = b )
+
+ I think that last works. () might almost be optional
+ .foo=a
+ is an expression means a structure with a .foo field assined to 'a'
+ [3] = 2
+ is an array for at least 4 elements with 4th set to 2.
+
- yet more operators
<< >> #
bit-ops & | ~ &~
- per-field attributes
constant, stable, add-only, read-only, mutable, owned, borrowed, dependant, pure
- records
-- enum
+- enum / set
- classes
- constructors and destructors - or "after" ??
+ destructors, which can be declared inline
- vtables, fat pointers, list of approaches
- operators as interface methods
+ + - * / etc make an arith interface add sub mult div
- interfaces, inheritance
- modules, imports and exports
+ public(version) on types, fields etc
- closures, threads, co-routines, generators
+- generics/templates. These should be just a compile-time
+ decision. Same code can be called with suitable methods passed, or
+ recompiled in the new context and then optimised.
- introspection / reflection ?
e.g. support serialization
find function given a string holding the name