panyam/onering issues and pull requests

#38 - Deprecate field paths. FQNs should suffice for dereferencing into anything.

Issue - State: closed - Opened by panyam about 7 years ago

#37 - Only generate the constructor to the variable in a function if there is no direct copy to it.

Issue - State: open - Opened by panyam about 7 years ago

#36 - Investigate whether externs should be part of a package export (and part of main.js) instead of having to be manually managed.

Issue - State: open - Opened by panyam about 7 years ago

#35 - Provide Java implementations of get_field_path and ensure_field_path

Issue - State: open - Opened by panyam about 7 years ago

#34 - Provide JS implementations for get_field_path and ensure_field_path

Issue - State: open - Opened by panyam about 7 years ago

#33 - Detect imports from dependant packages instead of having to explicitly specify them

Issue - State: open - Opened by panyam about 7 years ago

#32 - Annotation values to also pull in type applications

Issue - State: open - Opened by panyam about 7 years ago

#31 - Typefuncs

Pull Request - State: closed - Opened by panyam over 7 years ago

#30 - Create module container type instead of transformer/group/interface etc.

Issue - State: closed - Opened by panyam over 7 years ago - 1 comment

#29 - Provide language mapping/coercion of types which is used by AST and commands.

Issue - State: open - Opened by cheftako almost 8 years ago - 1 comment

#28 - Derive from multiple records.

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#27 - Investigate fall through case for "raw" types

Issue - State: open - Opened by panyam almost 8 years ago - 2 comments

#26 - Checking duplicate function signatures in platform bindings

Issue - State: closed - Opened by panyam almost 8 years ago - 2 comments

#25 - Allow grouping of function and type bindings by platform

Issue - State: closed - Opened by panyam almost 8 years ago - 3 comments

#24 - Give each parsed entry a URI to identify where it has been read from

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#23 - Make sure platform specific function names are used

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#22 - Capitalising Byte and Bool types

Pull Request - State: closed - Opened by panyam almost 8 years ago

#21 - Parametric types

Pull Request - State: closed - Opened by panyam almost 8 years ago

#20 - Come up with alternate template that works directly on expression tree to minimise generated local vars.

Issue - State: closed - Opened by panyam almost 8 years ago - 2 comments
Labels: enhancement

#19 - Better way of getting type signature using templates (int vs Int etc)

Issue - State: closed - Opened by panyam almost 8 years ago - 3 comments

#18 - Control where output for generator goes

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#17 - Dont generate models for master

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#16 - Give the names of source and dest variables for a transformer in the transformer declaration itself

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#15 - Make parsing of parametrized types generic

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#14 - Use TypeReference instead of Types directly when referring to types

Issue - State: closed - Opened by panyam almost 8 years ago - 2 comments

#13 - Making "constructors" in types be pluggable

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#12 - Proj classes

Pull Request - State: closed - Opened by panyam almost 8 years ago

#11 - Generate code for manual transformer rules (statements) between two records in a transformer.

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#10 - Generate a list of implicit transformer rules between two records if they are related.

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#9 - In a derivation or record, if a projected type does not have a name, give it auto-gen name

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#8 - Make annotations implicit instead of requiring a parse_annotations call.

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#7 - Adding floating point parsing rule to lexer

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#6 - onering dsl parser needs event handler on certain events.

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#5 - onering load command should not fail if same file is specified twice.

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#4 - Generate code for derivations with type streaming

Issue - State: closed - Opened by panyam almost 8 years ago

#3 - Add console command to generate a single files

Issue - State: closed - Opened by panyam almost 8 years ago - 1 comment

#2 - Add commands to register backends/languages and all things with it (templates, paths etc)

Issue - State: closed - Opened by panyam almost 8 years ago - 2 comments

#1 - Add console commands to load onering files

Issue - State: closed - Opened by panyam almost 8 years ago

Ecosyste.ms: Issues

GitHub / panyam/onering issues and pull requests

#38 - Deprecate field paths. FQNs should suffice for dereferencing into anything.

#37 - Only generate the constructor to the variable in a function if there is no direct copy to it.

#36 - Investigate whether externs should be part of a package export (and part of main.js) instead of having to be manually managed.

#35 - Provide Java implementations of get_field_path and ensure_field_path

#34 - Provide JS implementations for get_field_path and ensure_field_path

#33 - Detect imports from dependant packages instead of having to explicitly specify them

#32 - Annotation values to also pull in type applications

#31 - Typefuncs

#30 - Create module container type instead of transformer/group/interface etc.

#29 - Provide language mapping/coercion of types which is used by AST and commands.

#28 - Derive from multiple records.

#27 - Investigate fall through case for "raw" types

#26 - Checking duplicate function signatures in platform bindings

#25 - Allow grouping of function and type bindings by platform

#24 - Give each parsed entry a URI to identify where it has been read from

#23 - Make sure platform specific function names are used

#22 - Capitalising Byte and Bool types

#21 - Parametric types

#20 - Come up with alternate template that works directly on expression tree to minimise generated local vars.

#19 - Better way of getting type signature using templates (int vs Int etc)

#18 - Control where output for generator goes

#17 - Dont generate models for master

#16 - Give the names of source and dest variables for a transformer in the transformer declaration itself

#15 - Make parsing of parametrized types generic

#14 - Use TypeReference instead of Types directly when referring to types

#13 - Making "constructors" in types be pluggable

#12 - Proj classes

#11 - Generate code for manual transformer rules (statements) between two records in a transformer.

#10 - Generate a list of implicit transformer rules between two records if they are related.

#9 - In a derivation or record, if a projected type does not have a name, give it auto-gen name

#8 - Make annotations implicit instead of requiring a parse_annotations call.

#7 - Adding floating point parsing rule to lexer

#6 - onering dsl parser needs event handler on certain events.

#5 - onering load command should not fail if same file is specified twice.

#4 - Generate code for derivations with type streaming

#3 - Add console command to generate a single files

#2 - Add commands to register backends/languages and all things with it (templates, paths etc)

#1 - Add console commands to load onering files