chore: fix confusing Environment.replayConsts parameter order (#7472)
This commit is contained in:
parent
a014ae1001
commit
0f3d426591
1 changed files with 1 additions and 1 deletions
|
|
@ -1916,7 +1916,7 @@ but not `oldEnv` and the environment extension state for extensions defining `re
|
|||
`skipExisting` is true, constants that are already in `dest` are not added. If `newEnv` and `dest`
|
||||
are not derived from `oldEnv`, the result is undefined.
|
||||
-/
|
||||
def replayConsts (oldEnv newEnv : Environment) (dest : Environment) (skipExisting := false) :
|
||||
def replayConsts (dest : Environment) (oldEnv newEnv : Environment) (skipExisting := false) :
|
||||
BaseIO Environment := do
|
||||
let numNewConsts := newEnv.asyncConsts.size - oldEnv.asyncConsts.size
|
||||
let consts := newEnv.asyncConsts.revList.take numNewConsts |>.reverse
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue