Skip to content
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.

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

warning 61 shown in externals #415

Merged
merged 2 commits into from
Nov 13, 2022
Merged

warning 61 shown in externals #415

merged 2 commits into from
Nov 13, 2022

Conversation

jchavarri
Copy link
Member

Just showcasing another case where a warning that was added in recent versions (in this case 61 [unboxable-type-in-prim-decl]) appears on externals.

Not sure if this one in particular is something that could be fixed on Melange side, or it's maybe more documentation related, but I hope it's worth opening the PR for discussion.

@jchavarri
Copy link
Member Author

cc @anmonteiro @EduardoRFS

@anmonteiro anmonteiro marked this pull request as ready for review November 13, 2022 04:49
@anmonteiro anmonteiro merged commit 3552739 into main Nov 13, 2022
@anmonteiro anmonteiro deleted the warning-61-external branch November 13, 2022 05:26
anmonteiro added a commit that referenced this pull request Nov 13, 2022
anmonteiro added a commit that referenced this pull request Nov 13, 2022
anmonteiro added a commit to anmonteiro/opam-repository that referenced this pull request Nov 16, 2022
CHANGES:

- Disable warning 69 (`unused-field` in record) for the private record
  generated by the `bs.deriving` attribute
  ([melange-re/melange#414](melange-re/melange#414))
- Disable warning 20 (`ignored-extra-argument`) when applying
  `foo##fn arg1 arg2`
  ([melange-re/melange#416](melange-re/melange#416)):
  - in cases such as `external x : < .. > Js.t = ""`, the typechecker doesn't
    know the arity of the function, even though Melange will emit an uncurried
    function call.
- Disable warning 61 (`unboxable-type-in-prim-decl`) in `external` declarations
  ([melange-re/melange#415](melange-re/melange#415)):
  - Melange externals are substantially different from OCaml externals. This
    warning doesn't make sense in a JS runtime.
- melc: introduce `--bs-module-name` flag to specify the original file name for
  the current compilation unit
  ([melange-re/melange#413](melange-re/melange#413))
  - Dune's namespacing implementation generates modules such as
    `lib__Original_name`. Passing `--bs-module-name original_name` allows
    melange to issue correct `import` / `require` statements to the unmangled
    JS file names.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants