Radosław Rowicki
Radosław Rowicki
I can confirm the problem on my side with spacemacs. However, I have also a pure minimalistic emacs config where everything works as expected. I have a fresh spacemacs build...
Okay, removing `~/.emacs.d/elpa/develop/lcr-20180902.1919/lcr.elc` has fixed the problem
I can confirm the problem
Yet another real-life example: https://github.com/aeternity/hyperchains-contract/blob/master/contracts/Election.aes
@marc0olo The VS code extension is slightly outdated (eg it lacks `main` keyword and `
Yes, and I was asked to make it into an issue. Please check the last comment of the discussion you linked.
I absolutely see your point @svick. Making primitive or "common use" types implicit is definitely a misuse of implicit parameters in most cases. Although, should we always forcefully prevent writing...
> If only implicit parameters were allowed to be passed implicitly This is a key constraint of the design. You still need to *explicitly* indicate that some stuff is handled...
@Richiban You have a very good point. I think it would be a nice linter rule to enforce certain name convention for implicit-param types, such as what we have for...
I can dive then into the code, play a little bit and come back with some more detailed view on how I would see it implemented.