jimn
11/16/2021, 6:06 AM"<*>" will be illegal in 1.7
I came up with the notion that intellij is dominantly written in kotlin and kotlin has a PSI editor with syntax embedding which is therefore going to have significant export compatibility with kotlin as well, whether currently done or otherwise.
in my code I would if i could simply wrap C code into an embedding and accept a guided tour of compiler errors to flesh out the declaration gaps needed.
Instead I have been using sed and operator overloads to examine the gap and fill in the machinations that apparently already exist in a kotlin-native exports version of CPP.
This also got me to thinking that this python project was making some mention of the steep difficulties in porting while there sits volumes of presumably kotlin-friendly pycharm code.
The dichotomy appears unfortunate to me, that we pay and priotize editors which can perform language specific mappings while my experience proposing flexible language constructs in every language development conversation I have undertaken is almost always met with a summary that is not far from "we are very happy with how we solve programming problems and we feel that stability and usability excludes such matters".
but if that's the case then why is there in fact so much effort undertaken from scratch to build front-end harnasses for the language that our editor front-ends are already doing a spectacular job of?Piotr Krzemiński
11/16/2021, 9:09 AMjimn
11/16/2021, 9:12 AMPiotr Krzemiński
11/16/2021, 9:14 AMjimn
11/16/2021, 9:14 AMPiotr Krzemiński
11/16/2021, 9:16 AMjimn
11/16/2021, 9:16 AMPiotr Krzemiński
11/16/2021, 9:19 AMjimn
11/16/2021, 9:21 AMPiotr Krzemiński
11/16/2021, 9:21 AMjimn
11/16/2021, 9:23 AMPiotr Krzemiński
11/16/2021, 9:23 AMjimn
11/16/2021, 9:31 AMPiotr Krzemiński
11/16/2021, 9:32 AM