ityonemo/mavis issues and pull requests

#149 - type macro isn't quite right about some things

Issue - State: open - Opened by ityonemo about 3 years ago

#148 - Difference types

Pull Request - State: closed - Opened by ityonemo over 3 years ago

#147 - Refactor lists

Pull Request - State: closed - Opened by ityonemo about 4 years ago

#146 - property test to make sure that inspected components in a union are in type order.

Issue - State: open - Opened by ityonemo about 4 years ago
Labels: testing

#145 - make sure inspects of [] with generic types don't come out strange.

Issue - State: open - Opened by ityonemo about 4 years ago
Labels: bug

#144 - message simplification

Issue - State: open - Opened by ityonemo about 4 years ago

#143 - composable message scheme

Issue - State: open - Opened by ityonemo about 4 years ago

#142 - double check that floats don't cause problems in range type operations

Issue - State: open - Opened by ityonemo about 4 years ago

#141 - use rangeresolve(a, b) for more logic in the range module

Issue - State: open - Opened by ityonemo about 4 years ago

#140 - Literal types

Pull Request - State: closed - Opened by ityonemo about 4 years ago

#139 - 0.0.6

Pull Request - State: closed - Opened by ityonemo about 4 years ago

#138 - Refactor tuples

Pull Request - State: closed - Opened by ityonemo about 4 years ago

#137 - Refactor tuples

Pull Request - State: closed - Opened by ityonemo about 4 years ago

#136 - Type normalization

Pull Request - State: closed - Opened by ityonemo about 4 years ago

#135 - make sure that top_arity functions can be inspected.

Issue - State: closed - Opened by ityonemo about 4 years ago - 1 comment

#134 - remove inferred tag from functions

Issue - State: closed - Opened by ityonemo about 4 years ago - 1 comment

#133 - Union fixes

Pull Request - State: closed - Opened by ityonemo about 4 years ago

#132 - Union fixes

Pull Request - State: closed - Opened by ityonemo about 4 years ago

#131 - Subtraction types

Issue - State: open - Opened by ityonemo about 4 years ago

#130 - make a Function.Bundle type that isn't a union.

Issue - State: open - Opened by ityonemo about 4 years ago

#129 - adds the correct return type for Type.Inference.Api

Pull Request - State: closed - Opened by ityonemo about 4 years ago

#128 - now defaults to ignoring none() in unions.

Pull Request - State: closed - Opened by ityonemo about 4 years ago

#127 - create a type normalization function

Issue - State: closed - Opened by ityonemo about 4 years ago - 1 comment

#126 - make sure that types can be normalized on inspect

Issue - State: closed - Opened by ityonemo about 4 years ago - 1 comment

#125 - Switch to type macros

Pull Request - State: closed - Opened by ityonemo about 4 years ago

#124 - fix: unions with empty string

Issue - State: closed - Opened by ityonemo about 4 years ago - 1 comment

#123 - is_returnable/1 guard that selects against builtin(:none) and builtin(:no_return)

Issue - State: closed - Opened by ityonemo about 4 years ago - 1 comment

#122 - Create a builtin(:no_return) which is distinct from builtin(:none)

Issue - State: closed - Opened by ityonemo about 4 years ago - 1 comment

#121 - Type.union should switch to not treating builtin(:none) separately

Issue - State: closed - Opened by ityonemo about 4 years ago - 1 comment

#120 - check that deviations from standard elixir can be turned off.

Issue - State: open - Opened by ityonemo about 4 years ago

#119 - make sure that functions can merge their parameters if their return types match.

Issue - State: closed - Opened by ityonemo about 4 years ago - 1 comment

#118 - refactor the way to do default types:

Issue - State: closed - Opened by ityonemo about 4 years ago - 1 comment

#117 - make functions() type, change Type.Inference.Api

Issue - State: closed - Opened by ityonemo about 4 years ago - 1 comment

#116 - consider adding ability for tuples to have a fixed value?

Issue - State: closed - Opened by ityonemo about 4 years ago - 2 comments

#115 - 0.0.5

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#114 - Minimum arity tuple

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#113 - Minimum arity tuple

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#112 - Apply

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#111 - Top function type

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#110 - Revert "Top function type"

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#109 - Top function type

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#108 - Refactor to type macros

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#107 - reorder fields in maps to be syntatically correct.

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#106 - correct rules for tuple merging in unions

Issue - State: closed - Opened by ityonemo over 4 years ago - 5 comments

#105 - refactor to use list/1 instead of %Type.List

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#104 - Deprecate non neg integer

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#103 - refactor Tuple doctests to use Type.tuple/1

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#102 - refactor Map doctests to use Type.map/1

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#101 - deprecate Map.build in favor of Type.map/1 macro

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#100 - More builtins

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#99 - adds in is_singleton guard

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#98 - is it the case that if you take two terms then the type of the two terms will obey order?

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#97 - clean up inspect representation for confusing types

Issue - State: closed - Opened by ityonemo over 4 years ago - 2 comments

#96 - add in tuple with minimum arity type

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#95 - deprecate logic for non_neg_integer

Issue - State: closed - Opened by ityonemo over 4 years ago - 2 comments

#94 - function to dereference tuple type

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#93 - tuple with minimum arity

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#92 - apply for functions

Issue - State: closed - Opened by ityonemo over 4 years ago - 2 comments

#91 - add in more builtins

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#90 - add spec for functions with arity

Issue - State: closed - Opened by ityonemo over 4 years ago - 5 comments

#89 - add is_singleton guard

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#88 - move this from mavis_inference and put it into Type.of(<lambda>)

Issue - State: closed - Opened by ityonemo over 4 years ago

#87 - Misc doc changes

Pull Request - State: closed - Opened by kianmeng over 4 years ago - 1 comment

#86 - Fix source links in docs

Pull Request - State: closed - Opened by mbuhot over 4 years ago - 2 comments

#85 - 0.0.2

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#84 - make sure warnings for String.t are not confusing if one is fixed size.

Issue - State: open - Opened by ityonemo over 4 years ago

#83 - better documentation of type module

Issue - State: closed - Opened by ityonemo over 4 years ago

#82 - "deviations from elixir" in type module

Issue - State: closed - Opened by ityonemo over 4 years ago
Labels: deviations from erlang/elixir

#81 - consider making Type.Messages somehow nestable so that dependent typing information can be communicated

Issue - State: open - Opened by ityonemo over 4 years ago

#80 - make sure that Type.Messages can be inspect'ed to produce coherent error messages

Issue - State: open - Opened by ityonemo over 4 years ago

#79 - should the inference engine be a compile-time property or a runtime property?

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#78 - Documentation

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#77 - 0.0.1 task cleanup

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#76 - refactored type spec parsing to its own module

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#75 - Refactor typespec

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#74 - support for opaque types

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#73 - Foreign calls into own group

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#72 - Function variables

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#70 - makes sure typep works

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#64 - move Type.parse_spec/2 to its own module.

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment
Labels: refactoring, in progress

#63 - implement type caching system

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#62 - Detach inference and make its own library

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment
Labels: refactoring

#61 - Iolist

Pull Request - State: closed - Opened by ityonemo over 4 years ago

#57 - scan all standard library modules and make sure that mavis can parse their specs

Issue - State: closed - Opened by ityonemo over 4 years ago

#45 - break out intersection/usable_as macros out to their own module

Issue - State: closed - Opened by ityonemo over 4 years ago - 2 comments
Labels: refactoring

#42 - document the choice to deal with required/optional non-requirable types.

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment
Labels: documentation, deviations from erlang/elixir

#41 - test to make sure that typespecs for required non-requirable types are autoconverted to optional

Issue - State: closed - Opened by ityonemo over 4 years ago
Labels: deviations from erlang/elixir, testing

#35 - consider code reuse between Function.infer/1 and Function.asm/1

Issue - State: closed - Opened by ityonemo over 4 years ago
Labels: refactoring

#32 - Create Type.Api

Issue - State: open - Opened by ityonemo over 4 years ago

#31 - make unknown opcode emit the entire code stack.

Issue - State: closed - Opened by ityonemo over 4 years ago - 2 comments

#29 - make it possible for there to be an internal type, `String.t/1`

Issue - State: closed - Opened by ityonemo over 4 years ago - 2 comments
Labels: deviations from erlang/elixir

#25 - pruning errors

Issue - State: closed - Opened by ityonemo over 4 years ago
Labels: inference

#24 - basic backpropagation in sharded domain/range relationships

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment
Labels: inference

#23 - basic backpropagation on restricted output.

Issue - State: closed - Opened by ityonemo over 4 years ago
Labels: inference

#19 - function merging into unions.

Issue - State: closed - Opened by ityonemo over 4 years ago - 2 comments
Labels: wontfix

#14 - add "where's my builtin?" note

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment
Labels: documentation

#10 - make sure there are special checks against special subtypes

Issue - State: closed - Opened by ityonemo over 4 years ago - 1 comment

#6 - add nestable information for List maybes and errors

Issue - State: open - Opened by ityonemo over 4 years ago

#5 - add nestable meta-information for type.function matching.

Issue - State: open - Opened by ityonemo over 4 years ago - 2 comments

#1 - Figure out what do do with required() in maps

Issue - State: closed - Opened by ityonemo over 4 years ago - 2 comments
Labels: deviations from erlang/elixir

GitHub / ityonemo/mavis issues and pull requests