You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some (e.g. me) might want to use encoding’s interfaces and build decoders and encoders for their own encodings (e.g. see #68). Pulling in the whole encoding with all its supported encodings and their tables is not quite ergonomic, though, and splitting interfaces/types/traits out from the main crate would keep encoding as simple to use as it is currently and allow people to build on it.
The text was updated successfully, but these errors were encountered:
This allows for creation of alternative non-WHATWG encodings that use the same
interface as encodings defined in this crate without pulling in all the
tables and encodings.
This commit does not introduce any breaking changes; all the types previously defined in
encoding::types are reexported.
Fixeslifthrasiir#81.
This allows for creation of alternative non-WHATWG encodings that use the same
interface as encodings defined in this crate without pulling in all the
tables and encodings.
This commit does not introduce any breaking changes; all the types previously defined in
encoding::types are reexported.
Fixeslifthrasiir#81.
nagisa
added a commit
to nagisa/rust-encoding
that referenced
this issue
Jul 20, 2015
This allows for creation of alternative non-WHATWG encodings that use the same
interface as encodings defined in this crate without pulling in all the
tables and encodings.
This commit does not introduce any breaking changes; all the types previously defined in
encoding::types are reexported.
Fixeslifthrasiir#81.
Some (e.g. me) might want to use
encoding
’s interfaces and build decoders and encoders for their own encodings (e.g. see #68). Pulling in the wholeencoding
with all its supported encodings and their tables is not quite ergonomic, though, and splitting interfaces/types/traits out from the main crate would keepencoding
as simple to use as it is currently and allow people to build on it.The text was updated successfully, but these errors were encountered: