-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Provide a function to write the standard ebml header #2741
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Would this be the "EBML Basics" defined here? http://ebml.sourceforge.net/specs/ I don't see anything about "standard header" in the specs here, so I figured I'd ask for clarification. |
Visiting for triage. FIXME is still there but I have no idea what the standard header should be either. |
Triage: FIXME is still there; is the "standard header" the EBML Basics section of the Element Semantics table of @metajack's link? |
See also #9303, which will obviate this (since it will now be our own datatype, it will probably see a revamp and not have and weirdness like this) |
http://matroska.org/technical/specs/rfc/index.html, see section 5. This defines what we probably should be doing here. |
Given that this is entirely internal, this enhancement isn't going to be needed. And if it is, we'll add it. Closes rust-lang#2741.
…hton Given that this is entirely internal, this enhancement isn't going to be needed. And if it is, we'll add it. Closes rust-lang#2741.
Given that this is entirely internal, this enhancement isn't going to be needed. And if it is, we'll add it. Closes rust-lang#2741.
cargo-miri: use rustc to determine the output filename This should fix rust-lang/miri#2740 and fix rust-lang/miri#1867: we no longer need to hard-code the file name logic in cargo-miri.
cargo-miri: use rustc to determine the output filename This should fix rust-lang/miri#2740 and fix rust-lang/miri#1867: we no longer need to hard-code the file name logic in cargo-miri.
as per FIXME in std::ebml.
The text was updated successfully, but these errors were encountered: