ityonemo mavis_inference issues

ityonemo / mavis_inference

inference engine for mavis typesystem

1 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Make backprop 4

#61 ityonemo closed 3 years ago
0
Smarter freezing

#60 ityonemo closed 3 years ago
0
Disable erlang traversal

#59 ityonemo closed 3 years ago
0
make sure that freeze commands are tagged with the block line number

#58 ityonemo closed 3 years ago
1
implement an opcode macro for jump_to(meta, jump)

#57 ityonemo opened 3 years ago
0
Proper supervision

#56 ityonemo closed 3 years ago
0
implement automatically turning backpropped functions into Type.Function.Var values.

#55 ityonemo opened 3 years ago
0
consider taking advantage of type order in the ordering operators

#54 ityonemo opened 4 years ago
1
unify backprop to allow single register as well as list of register.

#53 ityonemo opened 4 years ago
0
stage 1.5 - full scan of elixir modules

#52 ityonemo opened 4 years ago
0
stage 1.4

#51 ityonemo opened 4 years ago
0
Dsl guards

#50 ityonemo closed 4 years ago
0
stage 1.3 - make sure that module compilation "really works"

#49 ityonemo opened 4 years ago
0
stage 1.2 - better dependency tracking

#48 ityonemo opened 4 years ago
0
make sure joker_vD's scenario works:

#47 ityonemo opened 4 years ago
0
consider being a bit smarter about fail codes

#46 ityonemo opened 4 years ago
0
opcode fusion

#45 ityonemo opened 4 years ago
1
consider making a more restrictive get_list backpropagation

#44 ityonemo opened 4 years ago
0
opcode push

#43 ityonemo opened 4 years ago
1
basic initial attempt at very bad caching

#42 ityonemo closed 4 years ago
0
Obtain type

#41 ityonemo closed 4 years ago
0
comprehensive review of the use of "state" variable

#40 ityonemo opened 4 years ago
0
make `test is_lt`, `gc_bif +` use typing functionals

#39 ityonemo opened 4 years ago
0
is_register_set(registers, param)

#38 ityonemo closed 4 years ago
1
create a way to generally put types

#37 ityonemo closed 4 years ago
1
Decouple call ext

#36 ityonemo closed 4 years ago
0
create a way to generally obtain types from arguments

#35 ityonemo closed 4 years ago
1
refactor infer/1 to be infer/3

#34 ityonemo opened 4 years ago
0
Refactor to registers

#33 ityonemo closed 4 years ago
0
Modular opcode modules

#32 ityonemo closed 4 years ago
0
add a guard in forward and backwards chain to make sure it's passed a registers struct.

#31 ityonemo closed 4 years ago
2
create a default "typespeccing chain" which searches for a typespec first, then does inference next.

#30 ityonemo opened 4 years ago
0
for opcode system if you try to match a variable

#29 ityonemo closed 4 years ago
1
refactor the Vm module to instead be called "Registers"

#28 ityonemo closed 4 years ago
1
add in a toggleable tracing function to both forward and reverse paths

#27 ityonemo closed 4 years ago
2
refactor to put metadata into its own path in the macros.

#26 ityonemo closed 4 years ago
1
allow 'when' statements in the opcodes

#25 ityonemo closed 4 years ago
7
Fwd back macros

#24 ityonemo closed 4 years ago
0
refactor "forward" and "backprop" directives to be macros instead of trapped macros

#23 ityonemo closed 4 years ago
1
test on single backprop event

#22 ityonemo opened 4 years ago
0
test on opcode unimplemented

#21 ityonemo closed 4 years ago
1
multiple use of variables in opcode to match can cause compiler warning

#20 ityonemo closed 4 years ago
1
variable rematching in "forward" keyword causes compiler warning.

#19 ityonemo closed 4 years ago
1
make opcodes be cascading

#18 ityonemo closed 4 years ago
1
Stage 1.2 make sure that history pruning is possible

#17 ityonemo closed 4 years ago
1
stage 1.1: get a demonstration of module typing completed.

#16 ityonemo closed 4 years ago
2
what happens if two internal functions tail call each other?

#15 ityonemo opened 4 years ago
0
create snapshot tests based on the erlang example

#14 ityonemo opened 4 years ago
1
some functions punt directly to nifs. Make sure there's a strategy to intercept these

#13 ityonemo opened 4 years ago
1
stage 5: create a strategy for testing opcodes as a unit test and putting them through at least one integration test

#12 ityonemo opened 4 years ago
0