I pushed an update yesterday that changes `pollen/markup` to ignore void values, the same way `pollen/pre` and `pollen/markdown` do.
So this file: #lang pollen/markup ◊(cond) Which used to parse this way: '(root <#void>) Will henceforth do this: '(root) I don't know why I had it the other way. Probably seemed like a good idea at the time. It wasn't. Anyhow, I don't think I'll characterize this as a "backward incompatible" change because: a) Void values were never valid in X-expressions, so the only sensible thing to do with them in `pollen/markup` was to filter them out. b) If you have existing code that filters out void values, this change won't break that code. c) If someone has code that affirmatively relies on detecting void values ... that just seems ludicrously unlikely, because the whole point of `void` is to disappear. But I've been wrong before. So if you have a counterexample to (c), let me know and I will consider rolling back the change. Otherwise, we'll just consider it a long-term wart, overdue for removal. -- You received this message because you are subscribed to the Google Groups "Pollen" group. To unsubscribe from this group and stop receiving emails from it, send an email to pollenpub+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
