On Fri, 9 Oct 2020 16:14:59 GMT, Ignasi Marimon-Clos
wrote:
> The API Docs for `BigDecimal` introduce the meaning of `scale`. The current
> writeup can be missleading when presenting the meaning of a `scale` value
> that's negative. Hopefully, with this PR, the sentence
On Fri, 9 Oct 2020 16:14:59 GMT, Ignasi Marimon-Clos
wrote:
> The API Docs for `BigDecimal` introduce the meaning of `scale`. The current
> writeup can be missleading when presenting the meaning of a `scale` value
> that's negative. Hopefully, with this PR, the sentence
On Wed, 5 May 2021 20:29:59 GMT, Brian Burkhalter wrote:
>>> @ignasi35 Do you wish to continue this PR? If so I will file an issue.
>>> Thanks.
>>
>> Hi @bplb, this completely fell through the cracks. If you could file the
>> issue for me I'd really appreciate it. Thanks.
>
> @ignasi35 I have
On Tue, 12 Jan 2021 14:07:23 GMT, Ignasi Marimon-Clos
wrote:
>> The `jcheck` test fails because "The commit message does not reference any
>> issue. To add an issue reference to this PR, edit the title to be of the
>> format `issue number: message`."
>
> T
On Mon, 4 Jan 2021 19:31:40 GMT, Brian Burkhalter wrote:
>> The API Docs for `BigDecimal` introduce the meaning of `scale`. The current
>> writeup can be missleading when presenting the meaning of a `scale` value
>> that's negative. Hopefully, with this PR, the sentence is more clear.
>>
>> Th
The API Docs for `BigDecimal` introduce the meaning of `scale`. The current
writeup can be missleading when presenting the meaning of a `scale` value
that's negative. Hopefully, with this PR, the sentence is more clear.
The ambiguity is on this sentence:
> If negative, the unscaled value of the
On Fri, 9 Oct 2020 16:14:59 GMT, Ignasi Marimon-Clos
wrote:
> The API Docs for `BigDecimal` introduce the meaning of `scale`. The current
> writeup can be missleading when presenting the meaning of a `scale` value
> that's negative. Hopefully, with this PR, the sentence
