eggyal
eggyal
For folding operations that cannot fail, the existing fallible folding trait is a little unergonomic. This PR introduces an infallible folder trait that can be used as a more ergonomic...
heck documents, under [Definition of a word boundary](https://docs.rs/heck/latest/heck/index.html#definition-of-a-word-boundary): > Characters not within words (such as spaces, punctuations, and underscores) are not included in the output string except as they are...
Because [`rustc_codegen_cranelift::driver::jit::run_jit`](https://github.com/bjorn3/rustc_codegen_cranelift/blob/a606fdec730da2eb6f29230739cedb70ec3a7e0e/src/driver/jit.rs#L54) never returns, rustc never runs finalisation actions for jitted runs; e.g. the incremental compilation cache is not committed to disk (in particular, [`rustc_interface::interface::Compiler::enter`](https://github.com/rust-lang/rust/blob/5c029265465301fe9cb3960ce2a5da6c99b8dcf2/compiler/rustc_interface/src/queries.rs#L422-L452) never progresses from invoking the...
Currently, implementors of (for example) `ArchiveUnsized` must add *the correct version* of `ptr_meta` to their own dependencies. If `rkyv` were instead to re-export `ptr_meta`, or at very least the relevant...
There are a number of multibyte bugs in this library. 1. [`str_replace()`](http://www.php.net/manual/en/function.str-replace.php) is not multi-byte safe, yet is being used to [escape quote characters within SQL object identifiers](https://github.com/colshrapnel/safemysql/blob/master/safemysql.class.php#L547). This can...
Am I correct in understanding that: * `HashMap` items remain stable in memory unless/until the map needs to reallocate for change of capacity; and * references to contained items are...
I see that `cached-path` currently determines how to extract an archive according to its filename extension: https://github.com/epwalsh/rust-cached-path/blob/db8cafb061ec1ff561747026f5db4317bfbaff7d/src/archives.rs#L17-L23 The problem that I have is that some archives do not use the...
That is, could this library guarantee that the local data will not move until the `ThreadLocal` is dropped, permitting unsafe code to access the local data (using raw pointers) after...
Minor point, but would it be possible to expose an `unsafe` version of these functions that doesn't perform any length-check?
I'm seeing `TargetSharedLibrary::each` panic on OS X, because the first image header has 0-bias but findshlibs asserts it must be non-zero?