Jonathan de Jong
Jonathan de Jong
> You can use [SocketAddr::from_str](https://doc.rust-lang.org/std/str/trait.FromStr.html#tymethod.from_str) to parse it, get an error if it failed parsing, gain info if its ipv6, and also get the port and the ip seperately. >...
More or less; Make most errors in `ruma` be `thiserror` (with exceptions, ofc) This is to allow greater programmatic control to the users of the library to ascertain *why* and...
Together with https://github.com/ruma/ruma/issues/862, we could probably download the referred-to-pages, and do a CSS-select for every id-handle the fragments point to, to see if they're still valid. In other words, we...
I think it'd be nice if we have an issue template able to be filled out with [github's new issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository), so that people can quickly report / fill in...
Related to https://github.com/ruma/ruma/pull/589, as `ring` has been removed to support WASM, it might be worth looking into this later, as I've gauged an interest from `ring`'s maintainer that, in the...
At https://github.com/serde-rs/json/blob/7ca63e7d5acac348db55c4345cb199f9d658669f/src/error.rs#L240-L241; ``` /// Encountered nesting of JSON maps and arrays more than 128 layers deep. RecursionLimitExceeded, ``` I feel this is possible to encounter in the wild in matrix,...
(pseudocode) ```rs // in ruma #[derive(RumaEvent)] #[ruma(type = "m.some.event"] pub struct SomeEvent { #[ruma(name = "m.something")] something: String, } // in another library #[derive(RumaEvent)] // optionally, overwrite the event type;...
Currently, together with https://github.com/ruma/ruma/issues/842 and https://github.com/ruma/ruma/issues/868, we may want to investigate sytest and complement to find "historical" or otherwise "non-spec" disrepancies, and decide on a case-by-case basis what ruma should...
Shootoff from https://github.com/ruma/ruma/issues/914#issuecomment-1062690878, I think it'd be nice to have all issues here instead of having them as todos in the codebase, else they'll be largely forgotten.
I think it's possible to reduce the total amount of allocations that `resolve` has to do by a significant amount, by making sure that most intermediary values instead borrow from...