grain

grain copied to clipboard

Modulo Throws Misleading Error When Used On A Float

3

 In the image above i was using modulo and my Number value became a float, when i used modolo it gave me the error of `NumberNotIntlike: Can't coerce number...

spotandjake

Proposed by @spotandjake in discord and iterated on a bit. Graindoc should allow something like a `@baseUrl` attribute in the module declaration block and if specified, graindoc could built source-file...

phated

Type annotation shorthands?

10

Type annotations can get unwieldy pretty fast, with types like `List`. I think it would be pretty cool to have shorthands for common types, like `[]` for lists, maybe `?`...

ospencer

LSP: Support for go to definition navigation

3

Currently cmd clicking on function invocation does not go to function definition, similarly for module name as well. We could implement go to defination functionality for better developer experience

sanathusk

LSP: Add support for inlay hints

5

Many languages like Javascript/ typescript, rust(through rust-analyzer VS code extension) provide support for inlay hint in VS Code as shown below.inlay hint provides hints for type of variable defined in...

sanathusk

Same-module type alias unification issue

1

If I create a parameterized type alias and then create a weakly typed value of that type, unification does not occur: It's easy to tell here via `foo` still being...

ospencer

Char Unicode Data and Conversions

9

It would be useful for `Char` to support a variety of Unicode-aware query functions and conversion functions (`toUpper`, `isPunctuation`, etc). For example, these are the ones supported by Racket [here](https://docs.racket-lang.org/reference/characters.html#%28part._.Classifications%29)...

peblair

This was discussed in another issue, but I can't find it quickly so I wanted to open a top-level issue. If you find the discussion, please link. To improve LSP...

phated

Printers can be registered for exceptions, but these values are only shown when an error is thrown. `Exception.print()` should return the string value of an exception.

ospencer

Printers for exceptions can be registered via `Exception.registerPrinter`, which are used whenever an exception is thrown. Besides an `Exception.print()`, should the standard `toString` and `print` also use the registered printers?

ospencer