Marcin Cieślak
Marcin Cieślak
What could possibly be done portably is an interface to external file watcher that just feeds the file names via the standard input to libsass.
Well the problem is that `debug_ast` is probably affected by the very problem I am debugging: it uses dynamic_cast which seems to not do the right thing for the strings....
Thanks. Will look it up. So now we can get rid of this pretty confusing constructs like ``` if (dynamic cast...) { do something } else if (quote_mark) { do...
@mgreter Ok, I read a little on CRTP and frankly I don't see it applied there .... we just use plain old polymorphism (with virtual tables) and run time type...
Thanks! With CRTP we could actually get rid of dynamic cast, and break output.cpp into output methods for respective types... that would be awesome
Mini-documentation: https://github.com/sass/libsass/wiki/Live-trace-facility
> > Stack allocation is free but heap isn't; how is this an optimization? > > Out of stack issues? https://docs.microsoft.com/en-us/visualstudio/code-quality/c6262?view=vs-2019 There is nothing wrong per se in having 32KB...
It might, actually my first thought was that this is just a coincidence...
Since we build it anyway on AppVeyor what about just attaching the .exe and the .pdb automatically as the attachments to the release? A [related code from node-sass](https://github.com/sass/node-sass/blob/722e617e3006f26aac3664237fc27a56c4688caf/appveyor.yml#L76-L97) is available.
No problem, just wanted to know if there are any obstacles to do so.