On 12/12/16 Dec 12 -1:36 PM, Daniel Kochmański wrote:
Robert Goldman writes:
Currently pending for 3.2.0:
!59 Link objects only
This is a long-standing bug in ASDF misusing using ECL's builder. ECL now will sanitize it in builder, so if its not merged, building in ASDF may fail with an error in some cases (instead of producing not working binary).
!61 Remove *load-system-operation*
This bug is introduced by enabling load-bundle-op by default on ECL. Effectively it prevents from switching to bytecodes compiler at runtime (i.e after loading ASDF) - ASDF uses wrong operation in that case for loading.
MR removes the whole load operation switch interface (what fixes this issue). @Fare: I see nothing controversial with it (i.e nothing to add with the peer review).
This looks uncontroversial, but it also looks like it's relatively low payoff. How often do people actually switch to the bytecode compiler after loading ASDF as you suggest?
Right now I am limited to testing on Windows when I go down to our company headquarters, which I do at most 2/week. The earliest I would get back to test this is Friday. So if I wait to merge this, it's very likely to push the 3.2 release into 2017. Is this really that important, or can it wait till 3.2.1?