Skip to content
  • No due date Last updated almost 13 years ago

    Now that libclang works perfectly, I think its time to drop the non…

    Now that libclang works perfectly, I think its time to drop the non-libclang part of the plugin.

    The motivation behind this is that when fixing a bug in the libclang part, you also have to fix it on the non-libclang part. Same thing when you want to evolve some APIs (like the snippet one).

    I can't think of any problem that it will cause. Any idea ?