trillian

Well, that's a shame. I guess there's really nothing you can do in that case. By the way, I really appreciate your effort working on this client. Apart from this...

basically, spotify-qt has no way to ask the spotify api for the queue. this means that if anything outside spotify-qt made changes to the queue, it wouldn't be accurate anymore....

List of warnings generated by Asar ``` manual pass check: assembleblock.cpp:1030: Manual warn without argument (pass 2) assembleblock.cpp:1038: Manual warn with argument (pass 2) assembleblock.cpp:1054: \ Expecttitle mismatch, title checks...

brainstorming on discord got us to ``` for i from 0 to 15 ; code using !i endfor ``` which i'm personally pretty happy with (upper and lower bounds can...

i quite like the last 2 actually, though the do/end feels a bit out of place with existing if/while constructs. more consistent would be ``` for i = 1, 10...

i still don't like using endif for anything that isn't an if, so i'd make `end` the only possible ending for `for`, and allow `endif` for if/while only for backwards...

i think this was discussed on discord too, but basically, the next release will allow `assert label == $xxxxxx`. i personally think that's good enough for this use case, but...

[Code coverage generated by `gcov`](https://media.smwcentral.net/randomdude999/asar_coverage) This was generated by running the entire test suite with gcov enabled. The test coverage is surprisingly good. I'm quite sure it's possible to integrate...

It's more meant to show which lines are not executed at all when running the test suite, showing which ones are executed most often is just a neat extra feature.

i think the actual recommended solution is `optimize dp always` and `optimize address mirrors`. basically what is happening is that label references get expanded to long instructions which previously got...