Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / HigherOrderCO/Kind1 issues and pull requests
#50 - first part of docs edit
Pull Request -
State: closed - Opened by johnchandlerburnham almost 5 years ago
#50 - first part of docs edit
Pull Request -
State: closed - Opened by johnchandlerburnham almost 5 years ago
#49 - Fix type parameter inference example?
Pull Request -
State: closed - Opened by courajs almost 5 years ago
- 1 comment
#49 - Fix type parameter inference example?
Pull Request -
State: closed - Opened by courajs almost 5 years ago
- 1 comment
#48 - Example of using move with recursion?
Issue -
State: closed - Opened by courajs almost 5 years ago
- 1 comment
#48 - Example of using move with recursion?
Issue -
State: closed - Opened by courajs almost 5 years ago
- 1 comment
#47 - Fix mutually recursive types example
Pull Request -
State: closed - Opened by courajs almost 5 years ago
- 1 comment
#47 - Fix mutually recursive types example
Pull Request -
State: closed - Opened by courajs almost 5 years ago
- 1 comment
#46 - First erasure example in readme doesn't parse
Issue -
State: closed - Opened by courajs almost 5 years ago
- 2 comments
#46 - First erasure example in readme doesn't parse
Issue -
State: closed - Opened by courajs almost 5 years ago
- 2 comments
#45 - Use nonzero exit code for failed typechecks?
Issue -
State: closed - Opened by courajs almost 5 years ago
#45 - Use nonzero exit code for failed typechecks?
Issue -
State: closed - Opened by courajs almost 5 years ago
#44 - Add C WASM version of new runtime
Pull Request -
State: closed - Opened by michaelforney almost 5 years ago
- 5 comments
#44 - Add C WASM version of new runtime
Pull Request -
State: closed - Opened by michaelforney almost 5 years ago
- 5 comments
#43 - RangeError: Maximum call stack exceeded on String
Issue -
State: closed - Opened by LoPoHa almost 5 years ago
- 1 comment
#42 - Following instructions in documentation doesn't work
Issue -
State: closed - Opened by masaeedu almost 5 years ago
- 1 comment
#42 - Following instructions in documentation doesn't work
Issue -
State: closed - Opened by masaeedu almost 5 years ago
- 1 comment
#41 - feat: new forall client
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 1 comment
#41 - feat: new forall client
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 1 comment
#40 - [Documentation] IsEven 5 is possible because of float as Number
Issue -
State: closed - Opened by LoPoHa almost 5 years ago
- 2 comments
#40 - [Documentation] IsEven 5 is possible because of float as Number
Issue -
State: closed - Opened by LoPoHa almost 5 years ago
- 2 comments
#39 - Maisa/documentation
Pull Request -
State: closed - Opened by MaisaMilena almost 5 years ago
- 1 comment
#39 - Maisa/documentation
Pull Request -
State: closed - Opened by MaisaMilena almost 5 years ago
- 1 comment
#38 - WIP: WASM Numeric Operations
Pull Request -
State: closed - Opened by johnchandlerburnham almost 5 years ago
- 2 comments
#38 - WIP: WASM Numeric Operations
Pull Request -
State: closed - Opened by johnchandlerburnham almost 5 years ago
- 2 comments
#37 - ReferenceError: subst_name is not defined
Issue -
State: closed - Opened by LoPoHa almost 5 years ago
- 1 comment
#37 - ReferenceError: subst_name is not defined
Issue -
State: closed - Opened by LoPoHa almost 5 years ago
- 1 comment
#36 - feat: remade all changes
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 1 comment
#36 - feat: remade all changes
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 1 comment
#35 - feat: squash all non-merged changes
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
#35 - feat: squash all non-merged changes
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
#34 - fix: redeclaration of variable term in subst
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
Labels: status: bug
#34 - fix: redeclaration of variable term in subst
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
Labels: status: bug
#33 - Update inet images
Pull Request -
State: closed - Opened by MaisaMilena almost 5 years ago
#33 - Update inet images
Pull Request -
State: closed - Opened by MaisaMilena almost 5 years ago
#32 - feat: exec helper module with json call
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 3 comments
#32 - feat: exec helper module with json call
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 3 comments
#31 - feat: remake parametrized file loader with fix
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 3 comments
#31 - feat: remake parametrized file loader with fix
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 3 comments
#30 - Improve recursive functions on fm-lang (usability and expressivity)
Issue -
State: closed - Opened by VictorTaelin almost 5 years ago
- 1 comment
#30 - Improve recursive functions on fm-lang (usability and expressivity)
Issue -
State: closed - Opened by VictorTaelin almost 5 years ago
- 1 comment
#29 - simplify fm-lang by parametrizing the file loader
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 3 comments
#29 - simplify fm-lang by parametrizing the file loader
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 3 comments
#28 - Add fm-json module for JS-Formality interop
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 5 comments
#28 - Add fm-json module for JS-Formality interop
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 5 comments
#27 - fix: export to-js
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 1 comment
#27 - fix: export to-js
Pull Request -
State: closed - Opened by bamorim almost 5 years ago
- 1 comment
#26 - 'open' is deprecated, so I removed its mention from a compiler hint.
Pull Request -
State: closed - Opened by Erhannis about 5 years ago
#26 - 'open' is deprecated, so I removed its mention from a compiler hint.
Pull Request -
State: closed - Opened by Erhannis about 5 years ago
#25 - Running with -o/-O leads to different results than running without
Issue -
State: closed - Opened by LoPoHa about 5 years ago
- 2 comments
#25 - Running with -o/-O leads to different results than running without
Issue -
State: closed - Opened by LoPoHa about 5 years ago
- 2 comments
#24 - Recursive-function-definition syntax error leads to unhelpful compiler behavior
Issue -
State: closed - Opened by Erhannis about 5 years ago
- 12 comments
#24 - Recursive-function-definition syntax error leads to unhelpful compiler behavior
Issue -
State: closed - Opened by Erhannis about 5 years ago
- 12 comments
#23 - Maximum call stack size exceeded for self-referencing datatypes
Issue -
State: closed - Opened by johnchandlerburnham about 5 years ago
- 2 comments
#23 - Maximum call stack size exceeded for self-referencing datatypes
Issue -
State: closed - Opened by johnchandlerburnham about 5 years ago
- 2 comments
#22 - Review documentation
Issue -
State: closed - Opened by MaisaMilena about 5 years ago
- 3 comments
Labels: review docs
#22 - Review documentation
Issue -
State: closed - Opened by MaisaMilena about 5 years ago
- 3 comments
Labels: review docs
#21 - Update docs
Pull Request -
State: closed - Opened by MaisaMilena about 5 years ago
Labels: review docs
#21 - Update docs
Pull Request -
State: closed - Opened by MaisaMilena about 5 years ago
Labels: review docs
#20 - Documentation bug on `if`
Issue -
State: closed - Opened by Erhannis about 5 years ago
- 5 comments
#20 - Documentation bug on `if`
Issue -
State: closed - Opened by Erhannis about 5 years ago
- 5 comments
#19 - hello.fm fails to compile
Issue -
State: closed - Opened by Erhannis about 5 years ago
- 5 comments
#19 - hello.fm fails to compile
Issue -
State: closed - Opened by Erhannis about 5 years ago
- 5 comments
#18 - Why unnecessary cases in pattern matching? (Question)
Issue -
State: closed - Opened by freddi301 about 5 years ago
- 10 comments
#18 - Why unnecessary cases in pattern matching? (Question)
Issue -
State: closed - Opened by freddi301 about 5 years ago
- 10 comments
#17 - Formality-core visualization?
Issue -
State: closed - Opened by mbuliga about 5 years ago
- 4 comments
#17 - Formality-core visualization?
Issue -
State: closed - Opened by mbuliga about 5 years ago
- 4 comments
#16 - Haskell implementation
Issue -
State: closed - Opened by o1lo01ol1o over 5 years ago
- 9 comments
#15 - Improvement/use let or const over var
Pull Request -
State: closed - Opened by evaporei over 5 years ago
- 1 comment
#15 - Improvement/use let or const over var
Pull Request -
State: closed - Opened by evaporei over 5 years ago
- 1 comment
#14 - readme: fix usage to clone new repo owner
Pull Request -
State: closed - Opened by evaporei over 5 years ago
- 1 comment
#13 - README.md Usage part is pointing to maiavictor instead of moonad
Issue -
State: closed - Opened by evaporei over 5 years ago
#12 - Why use var instead of let or const?
Issue -
State: closed - Opened by evaporei over 5 years ago
#11 - Fix typo
Pull Request -
State: closed - Opened by Widdershin over 5 years ago
- 2 comments
#10 - No type error constructing incorrect Eq proof
Issue -
State: closed - Opened by emturner almost 6 years ago
- 2 comments
#9 - Expressing fusible functions elegantly may require structural recursion
Issue -
State: closed - Opened by VictorTaelin almost 6 years ago
- 1 comment
#7 - Pattern matching
Pull Request -
State: closed - Opened by gabriel-barrett almost 6 years ago
#6 - Haskell benchmark improvements!
Pull Request -
State: closed - Opened by Kesanov almost 6 years ago
- 4 comments
#5 - Haskell benchmark with ADT.
Issue -
State: closed - Opened by Kesanov almost 6 years ago
- 1 comment
#4 - Fix typo in `List` datatype
Pull Request -
State: closed - Opened by lqd almost 6 years ago
#3 - Any plans for type inference?
Issue -
State: closed - Opened by lostmsu almost 6 years ago
- 1 comment
#2 - Dot notation.
Issue -
State: closed - Opened by Kesanov almost 6 years ago
- 7 comments
#1 - Same syntax for type level and value level expressions.
Issue -
State: closed - Opened by Kesanov almost 6 years ago
- 8 comments