yunsong

Sharing an optimization idea for Decimal operations

4

[we](https://github.com/alpacahq) use this decimal library at production and it works really well for last a few years. The only minor complain is that some times (during profiling) we noticed that...

- It currently does not support `or` in guard at the moment. - Since "if ... else ..." would be compiled to `case ... x == false or x ==...

When a module implements an Elixir Behaviour, type check should be able to verify the type spec from Behaviour declaration.

from #8 and #9, we have basic support for union type and pattern match, like following: ```elixir @spec example({:a, t1} | {:b, t2} | {:c, t3}) :: any def example({:a,...

We should already be able to do type hint with `T.assert( expr :: type )`. For example, ```elixir map = %{} # type is empty map T.assert(map :: %{optional(String.t) =>...

- Support custom typespec in `type.exs` conf file. (kind of like type definitions from Typescript) - The scope of this custom typespec should be limited to the package. - It...

sometimes, we have external API that returns `decimal.Decimal`, and we need to convert these instances to `alpacadecimal.Decimal`. currently, we can do this converson via "string" (decimal.Decimal -> string -> alpacadecimal.Decimal)....