I’ve been doing a lot of that. Right now, I’m trying to figure out why an object has renamed properties when it didn’t used to.
One thing I discovered is that initializing properties causes Google Closure to mess up renaming much more than uninitialized ones. Not sure why that is. Harbs > On Jul 1, 2019, at 10:19 PM, Greg Dove <[email protected]> wrote: > > 'The latests compiler changes have really taken a LOT of my time' > > Sorry to hear that, I have been there myself in the past. Can I check: is > this still related to Vector? > The docs also explain ways to switch off the other newer things (such as > the implicit casts: js-complex-implicit-coercions, for example), in case > that makes a difference. > > > > > On Tue, Jul 2, 2019 at 6:53 AM Harbs <[email protected]> wrote: > >> Yes. Switching off the index checking seems to help. (partially. I’m still >> trying to track down why my app isn’t working) >> >> The latests compiler changes have really taken a LOT of my time… :-( >> >>> On Jul 1, 2019, at 9:46 PM, Greg Dove <[email protected]> wrote: >>> >>> ' Yes. Not sure how to reproduce t for you.' >>> >>> OK, thanks for confirming. Hopefully switching off the index checking >> works >>> for you for now. I will see if I can repro that either later today or >>> tomorrow. >>> >>> >>> >>> On Tue, Jul 2, 2019 at 6:44 AM Harbs <[email protected]> wrote: >>> >>>> Yes. Not sure how to reproduce t for you. >>>> >>>>> On Jul 1, 2019, at 8:37 PM, Greg Dove <[email protected]> wrote: >>>>> >>>>> Are you seeing the index checking code being generated with >>>>> '-js-vector-emulation-class=Array' set for all your builds? If so, >>>> that's >>>>> a bug, and I'd be keen to repro it and fix. >>>> >>>> >> >>
