Cédric MORIN

indeed. This is how things were when I started to maintain the project, and I focused on the technical part, not on the license part.

@cancerberoSgx just like you I never heard about Haxe before digging in that project and juste discovering the entire ecosystem. In fact at the begining my idea was also to...

@Tw1ddle thank you for the feedback. I know the sqip tool and the article from Jose M Perez which is my inspiration source. SQIP is not a solution for me...

@cancerberoSgx some more details About measurment: * this number is what I get on my development computer, so not using a fully optimised PHP * on the same computer, the...

FYI I was able to cut the computing time by about a half by replacing all Haxe structures like `_hx_array()` with native PHP arrays and using native PHP cloning instead...

Hi! I'm trying to fullfill this spec (https://github.com/sass/sass-spec/blob/master/spec/core_functions/map/remove.hrx#L155) in https://github.com/scssphp/scssphp/ but as map-remove signature is `map-remove($map, $key...)` this spec is in conflict with https://github.com/sass/sass-spec/blob/master/spec/non_conformant/scss-tests/091_test_function_var_and_splat_args_pass_through_keywords.hrx and https://github.com/sass/sass-spec/blob/master/spec/non_conformant/scss-tests/072_test_mixin_var_and_splat_args_pass_through_keywords.hrx that are in both...

Seems good to me. I will add that as far as SPIP is concerned and givien last internal talks about PHP version support I could manage that the 2.0 release...

@stof the next 3.3 release coming soon should require at least PHP 7.1 but maybe PHP 7.3 - we are considering both options and it's more about the future (dev&maintenance)...

I can agree with the final target but I think we can do that in a more incremental way than you’re exposing here. We could start by moving everything in...

That's seems good to me as long as we keep the master branch running and spec compliant all the way long, which is exactly what you are proposing in #211...