Philipp Schuster

also add content download time (requires http/1.1 header parsing)

4

will be more complicated, because it needs HTTP header parsing.. content encoding could be chunked for example.. I need to know the contents length, because the "read_to_end" (EOF) doesn't work...

I think this should be fairly easy with the `h2` and `h3` crates. Default should stay HTTP 1.1 but we can add `--http2` and `--http3` flags.

- [ ] wait for https://github.com/JelteF/derive_more/pull/192 to be released

Add ttfb

1

#### New App Submission - [x] I've read the [contribution guidelines](https://github.com/agarrharr/awesome-cli-apps/blob/master/contributing.md#readme). **Repo or homepage link:** https://github.com/phip1611/ttfb **Description:** ttfb is a CLI-Tool to measure the TTFB (time to first byte) of...

For example, SmBios Tag can be there multiple times. But we only offer getters to get each tag at most once. The API should be more flexible

multiboot2-header: construct header at build time [call for contribution]

2

It would be awesome to construct multiboot2-headers at runtime with macros. For reference: That's how you write a header in assembly language: https://github.com/rust-osdev/multiboot2/blob/main/integration-test/bins/multiboot2_payload/src/multiboot2_header.S

multiboot2: foundation for mutable reference to tags

2

This is the foundation for a mutable boot information and another approach than #140. By using the `NonNull` facility, we can ensure that the compiler will not optimize away any...

miri: improve current situation

2

In https://github.com/rust-osdev/multiboot2/pull/128, I added basic miri support. Due to the following issues, miri can't embrace all it's funcitionality: - Each test that uses the `cast_tag` (transitively) fails, as miri can't...

The InformationRequest header tag should be the only DST for the multiboot2 header stuff. The same mechanism as for the DSTs in the multiboot2 crate should be used.