Tako Schotanus
Tako Schotanus
> But either way, we'd be de-optimizing existing array based Lists I don't understand, how we'd be doing that?
On the mailing list @jvasileff said: > In theory I really like the idea of sdk module versions being fully independent, but in practice this will make it much more...
Btw, input needed from all involved: @gavinking @FroMage @tombentley @chochos @davidfestal @thradec etc
> why not simply a fourth number? Because for a user the difference between a 1.2.2.1 and a 1.2.2.2 is normally completely unimportant, a super minor relase, probably some uninteresting...
> If necessary, we could have a two-part version number of form -module-version, for example, 1.2.1-2.1. What advantage would that have and how would it be less of a "hell"?...
> I don't think it's a big deal. Ok, I'm not going to discuss this any further. We'll just go with 1.2.1.1 then. But I'm sure people are going to...
I didn't even know this thread existed, but although late I wanted to say +1 to: ``` if (is Present myResource) {…} if (is Absent myResource) {…} ``` @jdpatterson I'm...
Yes I saw something like this today too but wasn't able to reproduce. But now I can, thanks! I'll take a look at this because I think it might have...
Actually I have the feeling it's looking at the existing JS artifacts instead of the CARs.
Sure, it's quite a bit of work though. Are you volunteering? ;-)