New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Difference in behavior with inline and multi-line definition with type annotation #13

Closed

mmhelloworld opened this issue Nov 8, 2014 · 1 comment

Labels

bug

Member

mmhelloworld commented Nov 8, 2014

frege> type F = (forall b. [b] -> [b]) -> Int
type alias F :: ?

frege> g :: F -> Int; g f = undefined
4: application of g will diverge.
4: Type [b]->[b]
inferred from  g is not as polymorphic as
expected type  forall b.[b] -> [b]

frege> :{
> g :: F -> Int
> g f = undefined
> :}
function g :: ((forall b.[b] -> [b]) -> Int) -> Int

The text was updated successfully, but these errors were encountered:

mmhelloworld added the bug label

mmhelloworld mentioned this issue

Unexpected token "forall" while trying to parse a non function type Frege/frege#80

Closed

Member Author

mmhelloworld commented Nov 13, 2014

Fixed with Frege/frege-interpreter@04a9019 .

Both command line REPL and online REPL now support the following:

frege> type F = (forall b. [b] -> [b]) -> Int
type alias F :: ?

frege> g :: F -> Int; g f = undefined
function g :: ((forall b.[b] -> [b]) -> Int) -> Int

mmhelloworld closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment