While Go's profiling tools are great a giving low-level hints at where we lose performance, they are a bad fit for adopters of the framework. In Langium we've already implemented a profiler for parsing (down to individual parsing rules), linking and validation. We should be able to implement something similar for Fastbelt.
While Go's profiling tools are great a giving low-level hints at where we lose performance, they are a bad fit for adopters of the framework. In Langium we've already implemented a profiler for parsing (down to individual parsing rules), linking and validation. We should be able to implement something similar for Fastbelt.