The choice ahead: wether to make the code go through the rust parser every keystroke or not. Performance isn't supporting doing that, i'd rather focus the whole UI/editor stack to fit into 90-144hz timewindows instead. So that means im building a boring old editor first :)
There's also quite a bit of complexity (much of it around async) and some decisions that are quite different from ones you've made. I'm saying you can adapt pieces in spite of those differences, not that your editor should be just like xi.
-
-
Yea i'll take a look at the code. Honestly don't know what im going to do for tokenizing Rust just yet, im going to try the factory default (syn) as well
-
The factory default does 'approx' 3ms per kloc. Thats not super fantastic i have to say.
End of conversation
New conversation -
-
-
currently my plan is something excessively stupid like a high perf 'comment or string' mask pass that starts at the top, and for the rest do virtual viewport 'as you draw' tokenisation. and update that 'string or comment' pass incrementally based on detecting things that impact
-
Ha just read your 16ms thing ;) I'm upping the stakes to 7ms! :)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.