Use precision from contract if not explicitely specified for @tokenAmount

So that:

"Transfer `@tokenAmount(self, amount)` to `recipient`"`

returns the same as:

"Transfer `@tokenAmount(self, amount, true, (self.decimals(): int)` to `recipient`"

I’m happy to open a pull-request for this, I just want to check if this sounds meaningful to you.

[sohkai]

I really like this! I would only push for having precision be set with a default (2 or 3), so it’s fairly similar to the current behaviour, and using -1 or null to signify the precision as the token’s decimal range.

[schmidsi]

I like the ~! So here is my recommendation:

The parameter precision is undefined by default. Default behaviour is like former precision === token.decimals:

Value =>	Display
1000000000000000000	1
1000000000000000	0.001
1	0.000000000000000001

It is a sane default, no information gets lost ever and it safes space where possible. The only problem is: If one want to compare multiple values, usually in a table with right aligned values, one might need fixed decimals. This is where this parameter comes into play: one can set a fixed amount of decimals (like JavaScript’s toFixed):

Assuming precision is set to 3

Value =>	Display
1000000000000000000	1.000
1000000000000000	0.001
1	~0.000
1000000000000000001	~1.000

Whereas the “~” indicates that the value was rounded and some information is lost.

This would be a slightly breaking change unfortunately.

Thoughts?