Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: hyperium/http
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.2.6
Choose a base ref
...
head repository: hyperium/http
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.2.7
Choose a head ref
  • 8 commits
  • 12 files changed
  • 7 contributors

Commits on Apr 15, 2022

  1. Copy the full SHA
    ec616ed View commit details

Commits on Apr 16, 2022

  1. Make HeaderName::from_static const (#499)

    ... plus some clean-up.
    
    It was only after I came up with the scheme using
    `const fn from_bytes(&[u8]) -> Option<StandardHeader>`
    that I noticed the debug+wasm32-wasi version of `parse_hdr`, which had
    something very similar.
    
    While cleaning up that function, I realized it still would still panic
    if an attempted name was too long, which had been fixed for all other
    targets and profiles in #433.  Then, I thought it would be worth seeing
    if the use of `eq!` in the primary version of `parse_hdr` still made any
    difference.
    
    And, it would not appear so. At least not on x86_64, nor wasm32-wasi run
    via wasmtime.  I've run the benchmarks a number of times now, and it
    seems the only significant performance change anywhere is actually that
    of `HeaderName::from_static` itself, which now seems to run in about 2/3
    the time on average.
    
    Unfortunately, `const fn` still cannot `panic!`, but I've followed the
    lead from `HeaderValue::from_static`.  While that version required 1.46,
    this new function requires 1.49.  That is almost 8 months old, so
    hopefully this isn't too controversial!
    jeddenlea authored Apr 16, 2022
    Copy the full SHA
    d8b35db View commit details

Commits on Apr 25, 2022

  1. Copy the full SHA
    4fb67bc View commit details

Commits on Apr 26, 2022

  1. Copy the full SHA
    f4cff03 View commit details
  2. Copy the full SHA
    d82aa29 View commit details
  3. Copy the full SHA
    bd30ce0 View commit details

Commits on Apr 28, 2022

  1. From impls of PathAndQuery and Authority for Uri (#538)

    * From impls of PathAndQuery and Authority for Uri
    
    A Uri may logically hold only an Authority or only a PathAndQuery.
    Should an application want to make such Uris, it would be easier to
    safely create them by first making just an Authority or just a
    PathAndQuery, then cheaply convert them directly into a Uri.
    
    * Fix Uri docs
    
    The doc comments for `impl From<Uri> for Parts` actually described
    `Uri::from_parts`.
    jeddenlea authored Apr 28, 2022
    Copy the full SHA
    c1f309e View commit details
  2. v0.2.7

    seanmonstar committed Apr 28, 2022
    Copy the full SHA
    95ad79b View commit details
Loading