-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
make Ref(x) always construct a RefValue(x) object (#21527)
the old behavior is now directly a feature of `convert` only instead
- Loading branch information
Showing
4 changed files
with
19 additions
and
6 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
b57a592
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Executing the daily benchmark build, I will reply here when finished:
@nanosoldier
runbenchmarks(ALL, isdaily = true)
b57a592
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @ararslan
b57a592
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those are some pretty gnarly regressions – @rfourquet, are these the ones from your recent PR? @vtjnash, is it possible any of these are caused by this change?
b57a592
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At least the regressions in
appear real and unrelated to
@rfourquet
's recent work. Best!b57a592
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are the ones from the "set-like operations" PR which have been analyzed and are not real regressions, but my guess is that the other regressions, concerning essentially
BitSet
, are the combination of the "BitSet stores any Int" and one "random" PR which changes the generated streams for ranges: indeed, the newBitSet
would tend to allocate less initially, by using only as much space as necessary (using theoffset
field). But then, asymdiff!
operation will force to allocate space as new elements are added, when earlier those element would fall in the arleady pre-allocated space. In other words, the performance depend substantially on the specificBitSet
used for benchmarks, and those have been changed by the "random" PR.