Rahul Muttineni

@ror6ax This issue is still relevant yes, but the UI is slightly different since we don't have (recommend) sandboxes anymore b/c we have the `new-build` system which has a Nix-like...

I'm going to sketch an implementation for this so we can see where what limitations (if any) will arise from this. When the compiler sees something like this: ```haskell import...

If the retention policy is at least CLASSFILE for the `@Nullable` annotation, we can detect it. Currently, the plan for direct imports is that if you return an Object reference...

Because the java import mechanism will behave differently than the default import mechanism (which we will stick to keeping compatible with Haskell for now), I think requiring `import java` and...

@jneira It looks like the `Win32` package was being built so I don't think it's a long paths problem this time. It may be that both of you have different...

@jneira I remember there was a Cabal fix for this - can you link that here to track it? We'll try to port it sometime.

Thanks for the beautiful write-up, @NickSeagull! I agree, this looks quite feasible. I made the following edits to your original issue: - I moved the annotations into the types instead...

@NickSeagull Yes, the java annotation declaration was made keeping in mind that we'd eventually support annotations for exports. Right now that is used for parsing the `@` notation for JWTs,...

By the way you should parse annotations *exactly* like Java does (keeps things consistent): https://docs.oracle.com/javase/specs/jls/se7/html/jls-18.html

> Annotations should not exist at the Core level, since annotations don't affect the code-generation process. Annotations should exist at the HsSyn level and should disappear as soon as the...