Skip to content
This repository has been archived by the owner on Dec 1, 2022. It is now read-only.

fix and simplify SubscriptRangeExpression's eval() #593

Merged
merged 3 commits into from
Jul 26, 2021

Conversation

jievince
Copy link
Contributor

  1. simplify the code;
  2. fix the wrong eval for this case:
return [0,1,2,3,4,5][-2..]

wrong result:
[4]
proper result:
[4,5]

@jievince jievince added the ready-for-testing PR: ready for the CI test label Jul 26, 2021
@jievince jievince requested review from Shylock-Hg and a team July 26, 2021 02:02
@jievince jievince requested a review from yixinglu July 26, 2021 09:50
@yixinglu yixinglu merged commit d58064e into vesoft-inc:master Jul 26, 2021
@jievince jievince deleted the fix-subscriptrange branch July 31, 2021 13:17
CPWstatic pushed a commit to CPWstatic/nebula-common that referenced this pull request Aug 2, 2021
CPWstatic added a commit that referenced this pull request Aug 2, 2021
* Modify the return value of partId function (#591)

* fix and simplify SubscriptRangeExpression's eval (#593)

* Fix toInteger() (#595)

* Fix toInteger/toFloat parsing string

* Check toInteger() overflow when  parsing string

Co-authored-by: laura-ding <48548375+laura-ding@users.noreply.github.com>
Co-authored-by: jie.wang <38901892+jievince@users.noreply.github.com>
Co-authored-by: Yichen Wang <18348405+Aiee@users.noreply.github.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ready-for-testing PR: ready for the CI test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants