We have Mutable and Immutable Array and Str .. how about Numbers?

[iamdadmin]

Description

Is it worth having Mutable and Immutable Numbers too?

Would we have it as Tempest\Support\Num with a collection of subtypes instantiating a common interface/trait with types int|float|etc ... would we support somewhat meta-types like IP Address, Hex, Binary? Currency with intl?

Would Uuid be a type of Num and be handled in this as well?

And if any of this sounds good have I just volunteered myself?

[innocenzi]

Personally I don't really see the use case. Arrays and strings have immutable/mutable versions because it's common to manipulate them (remove/add items from arrays, preprend/append to a string and other manipulations), and it's nice to have the mental model of knowing that manipulating them won't affect the original variable. But that's not something particularly useful for other scalars imo

[iamdadmin]

Personally I don't really see the use case. Arrays and strings have immutable/mutable versions because it's common to manipulate them (remove/add items from arrays, preprend/append to a string and other manipulations), and it's nice to have the mental model of knowing that manipulating them won't affect the original variable. But that's not something particularly useful for other scalars imo

The benefit I guess is mutable and immutable type safety. Which can be addressed in other ways I admit. They’re definitely not going to be used AS much just because of the data types involved being used proportionately less than strings and arrays.