-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
getopt doesn't handle missing spaces for single character options #2791
Comments
ghost
assigned jdm
Jul 4, 2012
jdm
added a commit
to jdm/rust
that referenced
this issue
Jul 4, 2012
…reat the remainder of the current option string as the argument if it is non-empty. Fix rust-lang#2791.
RalfJung
pushed a commit
to RalfJung/rust
that referenced
this issue
Feb 26, 2023
Get Miri working on ARM - Add a shim for `llvm.arm.hint`, which is required by `core::hint::spin_loop` on `arm` targets. The shim simply calls `yield_active_thread` on a YIELD hint, just like the shim for `llvm.aarch64.isb` that's already present. - Change the signature of `miri_host_to_target_path` to use `c_char` instead of `i8`, to make it compatible with `CStr` on targets where `c_char` is unsigned. The implementation of `miri_host_to_target_path` accesses the memory as bytes and does not need to be adjusted. - Enable ARM targets in CI. Specifically, `aarch64-unknown-linux-gnu` and `arm-unknown-linux-gnueabi` on the Linux host. Since all tests also pass for `aarch64-unknown-linux-gnu` I took the liberty of adding that target to CI as well. Fixes rust-lang#2791
celinval
added a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
Change the template to be more concise to address the team's concern that the template was too verbose. The new template is also cleaner since we are now using the PR description as the base for the commit message. --------- Co-authored-by: Michael Tautschnig <[email protected]> Co-authored-by: Zyad Hassan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should handle this properly.
The text was updated successfully, but these errors were encountered: