95833

the target of inline is to solve the priority of matching lexer along with the process of syntax parsed. And i don't know whether or not it can realized and...

I am fixing some bugs, so I have temporarily closed it.

Alright, it should now be usable to some extent. At least on the surface, it seems that no new trouble have been introduced.

There are still some bugs, but I am unable to fix them. for example:  When I click on it, it opens a path that is not the displayed one,...

I use it in the WSL environment, but it is a general feature. clangd also has a path mapping option, and their functions should be consistent. However, clangd also has...

Most of the code should be provided by @rwols , I am just using his code to meet some of my needs. He is more familiar with this part of...

With Copilot's help, I changed create_lexer to ``` template constexpr void create_lexer(std::index_sequence) { regex::dfa_builder b(lexer_sm); auto try_add_impl = [&b, this]() constexpr { using Term = std::tuple_element_t; if constexpr (has_get_data::value) {...

``` #include #include #include "ctpg.h" using namespace ctpg; using namespace ctpg::buffers; constexpr nterm list("list"); constexpr char number_pattern[] = "[0-9]+12"; constexpr regex_term number("number"); int to_int(std::string_view sv) { int i = 0;...

In addition, I’m not sure whether it is expected behavior that the regular expression . also matches newline characters.

It would be ideal to support **^** and **$** for recognizing the beginning and end of the string.