Kane York

update: after sending it through https://rawgit.com/tabatkins/parse-css/master/example.html I see that it does indeed emit a BAD-STRING, terminating at the newline. It would be nice to get the actual BAD-STRING token.

Your README points users to the main branch as the normal use - please consider a backport for those users.

> and (3) The open_pdks default install path /usr/share/pdks/. > > Currently I am not intending to support some hidden (or otherwise) subdirectory of $HOME other than what can be...

+1 the effect on codegen blowup should be documented properly

> cannot load such file -- kramdown-parser-gfm Looks like solidly not my fault.

MDN seems to think that support for HEAD is mandatory: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405 > Note: The two mandatory methods, GET and HEAD, must never be disabled and should not return this error...

Yes, I was alerted to this via the blink-dev Intent To Ship where they say Mozilla also intends to implement it. Intent to Implement: https://groups.google.com/a/chromium.org/d/topic/blink-dev/TQN4jWHydTk/discussion Intent to Ship: https://groups.google.com/a/chromium.org/d/topic/blink-dev/7MCjXU3zmCQ/discussion Chrome...

Yes, you can ping @estebank @pnkfelix @wesleywiser to check their boxes. (Stabilization PR is https://github.com/rust-lang/rust/pull/115717 .)

FullPath is already being used as the span name, so that half of this ticket can be ignored.

Also, consider releasing a new alpha3 version of your crate to benefit from crater-alikes checking the current version of your code :slightly_smiling_face: