Eliza Weisman
Eliza Weisman
Hmm – and this is probably a terrible idea, just something that popped into my head – what if requesting a cap got you back a sort of kernel mode...
> a quick glance at the seL4 FAQ would suggest that they actually have the kernel do the bookkeeping for caps and don't rely on crypto... I'm getting the sense...
yeah we definitely should have a nice source of randomness in kernel space regardless.
Another way we could potentially improve safety is by 'downgrading' some `*mut` pointers to `*const` pointers. Potentially, there might also be some `*const` pointers that could be downgraded to `&'static`...
This is probably not a very difficult refactor, and it'd be great if someone wanted to take it on as their first contribution. I can give pointers if necessary.
> I _think_ this can be resolved by making ansi formatting a const generic on `FormatFields`, but that might be a breaking change to `tracing-subscriber`. Yes, changing the type of...
why does this need to be pointed at the `valuable` branch?
@jswrenn any updates on this?
I'd like to get this one merged before cutting another `tracing-core` release, so, if you don't mind, I'm just going to go ahead and take care of the remaining docs...