Open
Conversation
Member
|
А ако някой освен BigDecimal + String ползва String + BigDecimal, т'ва не означавали че трябва да се monkey-patch-нат и двата? |
Member
|
Продължавам да не разбирам защо просто не се пуснат стария + новия spec и да се вземе max от 2та резултата? |
Author
|
@kunev По същата логика следва да се предефинират всички възможни аритметични операции. Току-виж някой умножава по коефициент, или пък някой може да прави -coupon_discount + price и т.н. На мен лично не ми се занимава. :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Monkey-patch-нал съм BigDecimal, предефинирал съм + и - за да работят и с низове. Моето решение (работещо с променения spec) и решението на Мартин (счупено от новия spec) минават. Не съм тествал повече. :)
NO WARRANTY и т.н. :)