You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of Rowan3 commit the semantics of the RwProject>>reload method has changed. The new semantics are that just the changed packages are loaded and any changes to load specifications are ignored ... this changes makes the #reload method more generally useful as there are certain corner cases where the old semantics could produce unexpected/unwanted results.
Occasionally, it is desirable to reread the load specs and packages since something may have changed in the specs that the user wants to pick up ... assuming that the user didn't use any custom projectsHome manipulation a simple reload specs menu item could be offered when it is necessary to pick up changed specifications from disk ...
If users have customized their loading process, the new implementation of reload is perfectly save, while the old variant was not safe ... of course the reload specs menu item would not be safe if custom loading has been done and we may want to have a warning ...
This is a placeholder so that sometime in the future we can discuss what we want to do ... to support this not completely uncommon use case ...
The text was updated successfully, but these errors were encountered:
As of Rowan3 commit the semantics of the RwProject>>reload method has changed. The new semantics are that just the changed packages are loaded and any changes to load specifications are ignored ... this changes makes the #reload method more generally useful as there are certain corner cases where the old semantics could produce unexpected/unwanted results.
Occasionally, it is desirable to reread the load specs and packages since something may have changed in the specs that the user wants to pick up ... assuming that the user didn't use any custom projectsHome manipulation a simple
reload specs
menu item could be offered when it is necessary to pick up changed specifications from disk ...If users have customized their loading process, the new implementation of reload is perfectly save, while the old variant was not safe ... of course the
reload specs
menu item would not be safe if custom loading has been done and we may want to have a warning ...This is a placeholder so that sometime in the future we can discuss what we want to do ... to support this not completely uncommon use case ...
The text was updated successfully, but these errors were encountered: