CAUTION: PERFORMANCE SUPERCHARGED! :zap: :zap: :zap:

Not really sure what's goin' on, but tests all passed, who knows

DO NOT MERGE THIS! WAIT UNTIL PARSER TESTS ALL PASSED!

Signed-off-by: CGQAQ [email protected]

main branch

Gnuplot not found, using plotters backend
small css file 7K       time:   [603.07 us 620.45 us 639.07 us]                              
Found 1 outliers among 100 measurements (1.00%)
  1 (1.00%) high severe

large css file 201K     time:   [13.683 ms 13.894 ms 14.094 ms]                                
Found 15 outliers among 100 measurements (15.00%)
  15 (15.00%) low mild

current branch

small css file 7K       time:   [149.54 us 164.43 us 181.72 us]                              
                        change: [-80.187% -76.213% -72.627%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 14 outliers among 100 measurements (14.00%)
  2 (2.00%) high mild
  12 (12.00%) high severe

large css file 201K     time:   [9.1747 ms 9.4870 ms 9.8056 ms]                                
                        change: [-34.236% -31.719% -28.996%] (p = 0.00 < 0.05)
                        Performance has improved.

Hi, I thought about a rust implementation of postCSS for quite some time and I'm glad this attempt exists. I am a beginner in Rust and while I was able to put together a basic parser using nom, I recon when it comes to visiting and changing the AST I do lack lot of experience with some Rust idiomatic patterns and especially memory management...

I still would like to learn more of the language and I see this project is definitely one I'd like to keep an eye on and eventually contribute to, I do maintain a CSS framework based on postcss-modules and on the long term I'd love to migrate it to rust to make it faster.

I opened this ticket to try and get an overview of the status of the project and how to best contribute.

1. Is the project currently actively developed? Is there a tentative roadmap or list of known issues/tasks beside the missing plugins?
2. Would be great to have a contributing guide, a basic description of the architecture and especially a guide to write plugins that may be the most approachable area for external contributors
3. I am also curious about the plugin API in general, in my mind I envisioned both a Rust API with some Plugin trait with a stable API, as well as maybe a way to use WASM compiled plugins as that may open the door to a larger community and possibly better integration with JS based pipelines (even though most likely lower speed). I wonder if this is something that was discussed and what are your thoughts about it

this branch

Gnuplot not found, using plotters backend
recursive_parser/small(7K)                                                                            
                        time:   [42.298 us 42.547 us 42.754 us]
                        change: [-20.656% -19.481% -18.441%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 11 outliers among 100 measurements (11.00%)
  11 (11.00%) low mild

Benchmarking recursive_parser/large(201K): Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 7.2s, enable flat sampling, or reduce sample count to 50.
recursive_parser/large(201K)                                                                             
                        time:   [1.0933 ms 1.1002 ms 1.1058 ms]
                        change: [-19.383% -17.867% -16.332%] (p = 0.00 < 0.05)
                        Performance has improved.

main branch

recursive_parser/small(7K)                                                                            
                        time:   [51.944 us 52.056 us 52.149 us]
                        change: [+21.004% +22.630% +24.207%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 11 outliers among 100 measurements (11.00%)
  10 (10.00%) low severe
  1 (1.00%) low mild

Benchmarking recursive_parser/large(201K): Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 8.3s, enable flat sampling, or reduce sample count to 50.
recursive_parser/large(201K)                                                                             
                        time:   [1.3027 ms 1.3081 ms 1.3125 ms]
                        change: [+18.758% +20.880% +23.165%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 9 outliers among 100 measurements (9.00%)