1 This is a living document - delete things when done. Avoid discussion.
3 Current version (Cataract Creek)
4 - functions to return type with 'use'
5 - functions to return structure with name assignment - bare 'use'?
6 - '?' prefix operator returns Boolean
7 - reference to struct (@foo), with @new, @free, @nil
8 - more number types, no units yet
16 - const fields ... what does that mean? Assign once as initialization?
17 Can be used for array size? What else?
18 - anonymous field - array or struct (or pointer to these)
19 multiple anon struct are allowed if they don't conflict
20 no - transparent fields! They still have a name, but you can
22 - [] can apply to transparent array field
23 - transparent struct field gets fields interpolated
25 - How to give attributes? just say the word?
30 - manifest values for arrays and structs [a,b,c]
31 or [.foo=a, .bar=b] or [ [1]=a, [2]=b]
32 That last doesn't parse easily, unless we require tags... not a good idea.
33 [ .[1] = a, .[2] = b ] ?? Maybe.
34 or () to group, [] for index. To (.foo=a) ( [1] = b )
36 I think that last works. () might almost be optional
38 is an expression means a structure with a .foo field assined to 'a'
40 is an array for at least 4 elements with 4th set to 2.
46 - integers, unsigned, bitfield, float, double?
49 - pure, loaded, overloaded, augmented
50 - owned: once, counted, collected
51 - shared or thread-local
53 - array buffer - can be added to and grows.
54 - char, string search, regexp search
56 - allow "do stuff" as a stand-alone statement (scope)
57 - 'use' labels *must* appear in case statements.
59 Next version (Govetts Creek):
60 - functions and procedures
61 - Finalize what a "main" program looks like.
64 - per-field attributes
65 constant, stable, add-only, read-only, mutable, owned, borrowed, dependant, pure
69 - constructors and destructors - or "after" ??
70 destructors, which can be declared inline
71 - vtables, fat pointers, list of approaches
72 - operators as interface methods
73 + - * / etc make an arith interface add sub mult div
74 - interfaces, inheritance
75 - modules, imports and exports
76 public(version) on types, fields etc
77 - closures, threads, co-routines, generators
78 - generics/templates. These should be just a compile-time
79 decision. Same code can be called with suitable methods passed, or
80 recompiled in the new context and then optimised.
81 - introspection / reflection ?
82 e.g. support serialization
83 find function given a string holding the name
84 measure coverage, adjust based on performance metrics
85 auto-create mock objects
86 Is this just parsing the details in the obj file?
88 - string / slice / strbuf
89 - parsing library - sscanf equiv, regexp, LALR
92 - sockets / http / HTML
93 - parameterised types, and dependant types
94 - message passing primitives
95 - overloading for numbers
97 - ensure list_head type concept can work
99 - pattern matching for destructuring??
102 - iso suffixes for number?
104 - case fall-through or go-to
105 - break/continue or "next","last"