Closed mahemoff closed 7 years ago
Hmm, maybe I can fix this and I'll consider to do so.
By the way, all of them are also bugs of Rubinius's header for C API.
Ahhhh, while I did some work for that https://github.com/k0kubun/hamlit/pull/104, I remembered the fatal thing. Rubinius doesn't provide ripper https://github.com/rubinius/rubinius/issues/2377.
Hamlit uses Ripper to parse Hash literal statically, thus it's very hard to port it. And personally, I don't like to use parser gem because (1) it is not standard library and requires additional installation effort, (2) it takes cost to update the gem version manually and otherwise it prints noisy warnings in not-supported Ruby versions.
I recommend you to use Haml 5.0.0.beta.2 instead. I did many improvements like https://github.com/haml/haml/pull/904 for Haml, keeping backward compatibility.
Hamlit is designed to have better performance than Slim. I'm maintaining Haml for various compatibility for many other use cases, including ones like you.
I'll support Rubinius in Hamlit once it implements Ripper.
I see. I had similar issues with some other native libs too, so can't use Rubinius for now anyway. Thanks for checking it @k0kubun
Using rbx-3.73 on OSX, I see ST_CONTINUE and UNLIMITED_ARGUMENTS are undefined.