Melody Horn

That schema corresponds to the KDL Schema specification, so the document that fits that schema is itself.

after a bit of experimentation, it seems like the `LINK_DELIM` approach you've taken doesn't gracefully handle what are in this case nested links. i'll throw in a pull request with...

https://github.com/rustwasm/wasm-bindgen/issues/1630 has been closed, making binary crates Just Work in `wasm-bindgen`; once those changes get released I'll see if I can push harder for `wasm-pack` to also Just Work on...

there's a draft implementation of this (and the proposed `serve` command from rustwasm/rfcs#10 as well) in #745, for what it's worth

this would be kinda nifty, i always saw pig.observer as filling a different role than more directly human-operated streams but i guess it'd be neat to have that supported anyway....

is there anything community members can do to help finalize this RFC? if we need more opinions about embedded vs external http handling, my opinion is that https://github.com/rustwasm/rfcs/pull/10#discussion_r263795579 is a...

Also worth noting is that per https://github.com/rust-lang/cargo/issues/7614 `cargo build --build-plan` is being removed, so `watch` will have to decide on its own which files should be watched.

I've thrown together a draft of a plausible implementation at https://github.com/rustwasm/wasm-pack/pull/745, partially out of curiosity and partially because @ashleygwilliams suggested that having a short turnaround time between design and implementation...

I am running into this issue with bindgen and I thought I could work around it with ```toml [patch.crates-io] bindgen = { git = "https://github.com/rust-lang/rust-bindgen", tag = "v0.50.0" } ```...

Surprisingly, that's already possible, as long as you know the full version of the crate: ``` PS D:\Melody\Projects\old projects\cargo-why> cargo why "libc 0.2.66" cargo-why -> failure -> backtrace -> backtrace-sys...