You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It provides many of its features by deeply integrating the ["DataDraw"](https://datadraw.sourceforge.net) tool into the primitives and constructs of the language. DataDraw is a code-generation tool that generates highly-optimized C code which outperforms e.g., the C++ STL given a declarative description of data-structures and relationships between them. For more information, see the [DataDraw 3.0 Manual](https://datadraw.sourceforge.net/manual.pdf).
29
+
It provides many of its features by deeply integrating features similar to the
30
+
["DataDraw"](https://datadraw.sourceforge.net) tool into the primitives and
31
+
constructs of the language. DataDraw is a code-generation tool that generates
32
+
highly-optimized C code which outperforms e.g., the C++ STL given a declarative
33
+
description of data-structures and relationships between them. For more
@@ -6,14 +6,14 @@ Add an option for generating SoA vs AoS memory layout so folks can do their own
6
6
Write a C or C++ backend code generator for improved debugging of Rune, and so folks can benchmark with
7
7
full front-end optimization of different C compilers for benchmarking.
8
8
Enhance gdb pretty printer so that we don't have to generate show methods.
9
-
Figure out when relationship generators should run. Right now it is in the order statements are bound so that module-level variables can be passed into the generators, but we assume all generators are run before binding a constructor, which is currently false. Figure out the right thing and do it.
9
+
Figure out when relationship transformers should run. Right now it is in the order statements are bound so that module-level variables can be passed into the transformers, but we assume all transformers are run before binding a constructor, which is currently false. Figure out the right thing and do it.
10
10
Use concrete type constraints in binding. This can help eleminate problems
11
11
in binding recursive functions, and also non-template classes.
12
12
Don't allow generated fields to be written outside of generated code.
13
13
Add an Object class that matches all types, so we can have case (Object, Object, Object).
14
14
Defend vs Spectre/Meltdown: duplicate bignum functions in runtime to have constant-time vs
15
15
non-constant time APIs. Do not pass in a secret bit.
16
-
Figure out how to programatically manipulate labels in generators.
16
+
Figure out how to programatically manipulate labels in transformers.
17
17
Flesh out index overloading: write is not yet supported.
18
18
Support Overloading method get/set methods.
19
19
Improve safe mode:
@@ -52,7 +52,7 @@ Support overloading modular operations, so we can support modular polynomials, e
52
52
Add multi-threading support.
53
53
Add schema-level reuse statements
54
54
Write a schema generator for Rune similar to the dataview program for DataDraw schemas.
55
-
Flush out generator's Rune code interpreter.
55
+
Flush out transformers's Rune code interpreter.
56
56
Finish transition to memory pools, and allocation of global arrays with mmap of the memory available on the machine so large arrays never move.
0 commit comments