Skip to content

Writing a translation to Gleam #212

@Nicd

Description

@Nicd

This is not an issue, I'm just contacting this way since I don't use X and this will be viewable by more eyes in one go. I'm currently writing an arbitrary precision decimal library for Gleam, which is currently lacking one, and it's nearly finished. Although it will be a separate library/package and thus won't burden the maintainers of this library, it's for the most part a translation of this library's code.

I will obviously follow the Apache license requirements and add attribution both in the source files and in license texts and the documentation. I'm really grateful for your work without which my version would not have been possible (although I've learned a lot about the math behind it while making and fixing my implementation).

The biggest difference will be in error handling, as raising errors is avoided in Gleam much more than in Elixir. To that end, many of the functions return results instead of raising, and there is no support for NaN or Infinity (they will be signaled with an error result). I was thinking I might add a separate API that wraps the default one but with NaN/Infinity semantics, though, as I figure some people might expect that support to exist.

Anyway, this was just a heads up and I figured I would ask if you have anything in mind that would be useful for me to know. I spotted #207 that I'll take into account, but if there's anything else that comes to mind, I'd be very grateful to hear it. :) Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions