Experimental unix shell that respects the user's configuration, even across SSH connections
My development branch for flazr
dhathorn/csci446-armada_skeleton 1
A skeletal Rails app to help bootstrap yours.
AdapterJS Javascript Polyfill and Tools for WebRTC - Skylink WebRTC
Simple extensive tar-like archive format with indexing
Avian is a lightweight virtual machine and class library designed to provide a useful subset of Java's features, suitable for building self-contained applications.
joshuawarner32/avian-website 0
Avian Virtual Machine website
push eventshepmaster/rust
commit sha a46679098f4d586b4fd46a63f6594b7282ea18cb
Add lint to warn about braces in a panic message.
commit sha 5b3b80a710bb9462541fc77f671b64e2651f1ec1
Allow #[rustc_diagnostic_item] on macros.
commit sha 462ee9c1b5eb0ae759e2fcc6f35dc5db4fc04367
Mark the panic macros as diagnostic items.
commit sha da66a501f6423d498627453dd7d0f8bc874ee42d
Specialize panic_fmt lint for the {core,std}::panic!() macros. It now only reacts to expansion of those macros, and suggests inserting `"{}", ` in the right place.
commit sha f228efc3f56ca13a4a969d0ee72c2e0844ac6a72
Make panic_fmt lint work properly for assert!(expr, msg) too.
commit sha 3beb2e95a98e90f43809a9ab1fb7175d4fa7aa8d
Expand assert!(expr) to panic() function instead of panic!() macro. The panic message might contain braces which should never be interpreted as format placeholders, which panic!() will do in a future edition.
commit sha 451c9864c498f715c39b52dbbf0c6258c608c13f
Add test for the panic_fmt lint.
commit sha ded269fa102df8716a540741ee7da6ce40e9738c
Improve panic_fmt message for panic!("{}") with a fmt placeholder.
commit sha b8a8b681b8ca37771a0116d7cc7c3e4e7c749e0e
Formatting.
commit sha 14dcf0a8ac632e6073ec979da72e286a57c50f4c
Test for formating placeholders in panic_fmt lint test.
commit sha dd262e385646fa94b85b5340f260efb01284261b
Add cfg(not(bootstrap)) on the new rustc_diagnostic_item attributes. The beta compiler doesn't accept rustc_diagnostic_items on macros yet.
commit sha 9615d27ab7327abdb2ba4aef5f797c693d02ef17
Don't see `{{}}` as placeholder in panic_fmt lint.
commit sha 9a840a30d68506a8070c309e5f8389a7ad09e55c
Fix brace problem in panic message in rustc_expand.
commit sha 0a9330c7ef1c4eb99e8143c7a586b1649ede85b8
Ignore panic_fmt lint in macro-comma-behavior-rpass ui test.
commit sha d3b41497fedc3362144aa3967b05987e278c376a
Also apply panic_fmt lint suggestions to debug_assert!().
commit sha f1fcc4dea319e1024b681f347cfb5ec307aaf743
Ignore panic_fmt lint in format-args-capture ui test.
commit sha dd81c9102863a9d8b965628c87cb639430d233f9
Update mir-opt test output for new assert macro implementation.
commit sha 9e3b949b8c43b43f38dd79dd2b9d6f600eec9ddb
Fix braces in panic message in test.
commit sha ff8df0bbe38d8b1216661c6544de4187e41eb45b
Add cfg(not(test)) to std_panic_macro rustc_diagnostic_item.
commit sha 0f193d1a62c128ae94e1f21d7c1212d7c9e95b7d
Small cleanups in assert!() and panic_fmt lint. (From the PR feedback.) Co-authored-by: Esteban Küber <[email protected]>
push time in 4 days
push eventshepmaster/rust
commit sha dcef5ff372742eb3d8a1b5cbbc2141e757bc33d1
Bump bootstrap compiler version
push time in 4 days
push eventshepmaster/rust
commit sha 9feb567399205879c80f9165ac8cdbcf547211da
Updated the list of white-listed target features for x86 This PR both adds in-source documentation on what to look out for when adding a new (X86) feature set and adds all that are detectable at run-time in Rust stable as of 1.27.0. This should only enable the use of the corresponding LLVM intrinsics. Actual intrinsics need to be added separately in rust-lang/stdarch. It also re-orders the run-time-detect test statements to be more consistent with the actual list of intrinsics whitelisted and removes underscores not present in the actual names (which might be mistaken as being part of the name)
commit sha cd95e939bb9bef598be54067e93ac712d43fba71
Removed movbe from run-time-detect `movbe` seems to not be a run-time detectable feature on x86. It has thus been removed from the list. It was only commented out to ease comparison against the full list.
commit sha 3daa93f555f4dab102da2a8d05cc38c4087166af
Updated documentation, x86 feature detection testing, and removed LLVM 9 exclusive features Updated the added documentation in llvm_util.rs to note which copies of LLVM need to be inspected. Removed avx512bf16 and avx512vp2intersect because they are unsupported before LLVM 9 with the build with external LLVM 8 being supported Re-introduced detection testing previously removed for un-requestable features tsc and mmx
commit sha 257ed899c86acf6b4ee0f6dc9d6cfc9eb98e35a5
Add tests
commit sha b025813f03033380f8761c1b0183fbe33884d3ec
Handle empty matches cleanly
commit sha d5a7ec0929dc438a78716585ceff827d51c8a32f
Unreachable subpatterns are rare We may as well leave early when we know there's nothing to report.
commit sha b9da2b372fb14c339779eeee02c9bb7468effc6d
Factor out match usefulness computation in `check_match` This make `_match` a lot more self-contained
commit sha 909c8945b172662494c0d0bd4cc89af618a41ffb
stability: More precise location for deprecation lint on macros
commit sha 55d7f736d8c62cc0a03594302538001ef3f3411d
Tighten the bounds on atomic Ordering in std::sys::unix::weak
commit sha 72b83af2ffadbc98fee52481c7168b0b644d73db
Re-enable LLVM 9 target features with LLVM 9 being the minimum now With #78848 merged, the minimum supported LLVM version is now 9 which means we can actually use the target features introduced in LLVM 9
commit sha 43bfbb10bf52d1cf6bd90ae2e19bcd357d38be4d
Add column number support to Backtrace Backtrace frames might include column numbers. Print them if they are included.
commit sha a015c21f163da6db9bfcb83ef1f503788041d9d5
Applied LLVM 9 fixes to LLVM 9 PR CI Dockerfile Now with LLVM 9 being the minimum supported version, we can finally remove the hacks in the dockerfile. This wasn't in the main PR bumping the version as I didn't quite understand what's going on and needed here.
commit sha b8f682b5e24625eedaa3874061c77bae131a27ae
Fixed missing / bad header when cross-compiling to i686 It seems that by default the 32-bit headers are not actually installed when installing development tooling. As we're using gcc headers, we need to install them as an extra package. See for reference: - https://stackoverflow.com/a/54082790 - https://askubuntu.com/a/106092 Also removed the now unused arm tooling
commit sha c82a258ad40ca8877e91a12722097e79a42905c6
Turn top-level comments into module docs in MIR visitor
commit sha 36e3409f6753fd92bf40608bc1d47c0de3161352
Apply suggestions from code review Co-authored-by: varkor <[email protected]>
commit sha dcc194ce2fb53555baf4bc16e5cacb3b5e1911b1
instrument `QueryNormalizer::fold_ty`
commit sha 7a15f026f2666a16255904879028acdd5513c766
linux: try to use libc getrandom to allow interposition We'll try to use a weak `getrandom` symbol first, because that allows things like `LD_PRELOAD` interposition. For example, perf measurements might want to disable randomness to get reproducible results. If the weak symbol is not found, we fall back to a raw `SYS_getrandom` call.
commit sha a035626eb53e88956680398f5fda821ca0e6bd97
Try weak symbols for all linux syscall! wrappers
commit sha cd22381daa7f23bf20a739ac35c95ff77921d9a0
Use syscall! for copy_file_range too
commit sha 69821cf8df86c8f4366e0c16a0a7de8d0135b90f
Add a test for foreign empty enums
push time in 4 days
push eventshepmaster/rust
commit sha 6967005e6e626f4ff62f53b971c00e6e12d2e618
Rollup merge of #78453 - Storyyeller:patch-1, r=jonas-schievink Fix typo in comments
commit sha a3bff691344ed94ca5ebab8a043141a0e56931d2
Use unwrapDIPtr because the Scope may be passed as None
commit sha db241bb0c8d257e13c1560f6250e49879477039e
Auto merge of #78458 - Dylan-DPC:rollup-tan044s, r=Dylan-DPC Rollup of 10 pull requests Successful merges: - #78152 (Separate unsized locals) - #78297 (Suggest calling await on method call and field access) - #78351 (Move "mutable thing in const" check from interning to validity) - #78365 (check object safety of generic constants) - #78379 (Tweak invalid `fn` header and body parsing) - #78391 (Add const_fn in generics test) - #78401 (resolve: private fields in tuple struct ctor diag) - #78408 (Remove tokens from foreign items in `TokenStripper`) - #78447 (Fix typo in comment) - #78453 (Fix typo in comments) Failed merges: r? `@ghost`
commit sha 4c58860cbfe51049d48f4f31f76dcc18b39cfe98
Fix suggestion to add unneeded space in `unused_unit`
commit sha 5b3d98d9f8d50a4bb3adf071dc6592cf458afbf1
Change link to point to crates.io keyword "hasher" Signed-off-by: Tom Kaitchuck <[email protected]>
commit sha 0217edbd292eeb9d5febfda6e33c574ab88cf916
Clean up intra-doc links in `std::path`
commit sha 2eb4fc800aaf5006f89af3af591e2aa34f469d81
Auto merge of #78323 - est31:smaller_list_overlap, r=varkor Iterate over the smaller list If there are two lists of different sizes, iterating over the smaller list and then looking up in the larger list is cheaper than vice versa, because lookups scale sublinearly.
commit sha 8e988e1c66eb775b9be9c1106911fa736872f313
Merge remote-tracking branch 'upstream/master' into sync-from-rust
commit sha dace756c6fa8793badbc9b872047cc539952e718
cargo dev update_lints
commit sha ffc2e666710cf5b6b97a162dfa01fc1fe4452af2
Fix reference
commit sha c90ef979de8cf63b895dfec0c12f1e12c049e1b6
fix a comment in validity check
commit sha b0df3f76dc70eba57d6e0665fa6ccac89b25d3aa
fix some incorrect aliasing in the BTree
commit sha 9e60f4511e39d012d5a21c10c55d706ec1e75e53
Add const generics tests for supertraits + dyn traits.
commit sha 5103a258aa806b4072c7081c6cb71a102979852e
Rustup to rustc 1.49.0-nightly (07e968b64 2020-10-27)
commit sha 6c73adf3240261315446582cb57de079bf2b87f9
Adjust turbofish help message for const generics
commit sha a6d01da7165d904d83407c385282803b9cb71dbb
Remove irrelevant FIXME
commit sha fab79c27ef184ee3620681bfbdc1fd89ad10b4df
Extend test to cover dyn methods/functions.
commit sha 22060fa0dc0f40652da875fd525e2a898c8584c5
Assert in every case.
commit sha 92fc1f8f9e0b38e6d292514a6f3a6e8627ae0cdc
build-manifest: include artifacts in a new table This commit adds to the generated manifest all files we ship that are not rustup components, namely: * Source code tarballs (rustc-{channel}-src.tar.xz) * Windows installers (rust-{channel}-{target}.msi) * macOS installers (rust-{channel}-{target}.pkg) Those files are included in a new "artifacts" table of the manifest, to avoid interfering with existing rustup installations.
commit sha f553c226c146d7233ce3b65973002643f5488715
Fix typo "compiltest"
push time in 6 days
push eventshepmaster/rust
commit sha 9412a898fa4ed5065a363bd40ad9401469ed3d54
Stabilize `Poll::is_ready` and `is_pending` as const Insta-stabilize the methods `is_ready` and `is_pending` of `Poll`. Possible because of the recent stabilization of const control flow. Also adds a test for these methods in a const context.
commit sha ce1d5ed31aff33bbbb116fffabd6107491c464bc
Move const tests for `Poll` to `library\core` Part of #76268
commit sha 34ff35298938f0d0ae477618b17a41d5afc00a7a
don't refer to async as 'generators' and give return of async fn a better span
commit sha 5042dbdb2e27b141ccc4cffc34efcf06ec24d59f
add RegionNameHighlight::Occluded
commit sha c027844795e427e63ef917ba40c71d0559d88b79
Fill in things needed to stabilize int_error_matching
commit sha 83d294f06a8f78f4956333a5285bb2c4f7b8a6a9
Bring char along with InvalidDigit
commit sha 8eaf0de1f45924a0fdbde00d4c7fe0333b377993
Remove incorrect plural
commit sha 1e7e2e40e4992a82b9e5bc7120bd33964bcef355
remove OnlySign in favour of InvalidDigit
commit sha f233abb9091e3c0999f0cb80ba652d6094e3d5b4
Add comment to helper function
commit sha a97abb40ab390465b1cd845e735d58956d28eb16
Rename LayoutErr to LayoutError in core
commit sha bf0adc3c36c255fd4dab690f9bdc369daf3e8825
Rename LayoutErr to LayoutError outside of core
commit sha 0266c134a724626506a256da58a982ea8a6e3ec8
Deprecate LayoutErr
commit sha 1d287255f57a6d42a44035ceb9861e96dfc5ee55
Change mention of `fnv` in HashMap to mention `aHash` as an alternitive hasher. Signed-off-by: Tom Kaitchuck <[email protected]>
commit sha 91a9f83dd1d73cfd451f81306361df3fafad84a5
Define `fs::hard_link` to not follow symlinks. POSIX leaves it implementation-defined whether `link` follows symlinks. In practice, for example, on Linux it does not and on FreeBSD it does. So, switch to `linkat`, so that we can pick a behavior rather than depending on OS defaults. Pick the option to not follow symlinks. This is somewhat arbitrary, but seems the less surprising choice because hard linking is a very low-level feature which requires the source and destination to be on the same mounted filesystem, and following a symbolic link could end up in a different mounted filesystem.
commit sha 5e80c65102f85700e1a449847dfa603e589df950
Bump version to 1.49.0 Due to the recent release of 1.47.0, this PR will be stabilized in 1.49.0 instead of 1.48.0.
commit sha 20e032e65007ff1376e8480c1fbdb0a5068028fa
Make it more clear when complaining about async fn's return types
commit sha 23a5c214150f462043ab411f87ef297309421d71
Fix a typo in a comment.
commit sha ce00b3e2e0c5c0c88fe59fb45a1c25a8ff9e1836
Use `link` on platforms which lack `linkat`.
commit sha 628fb9ff4a36c706789980276c165c4f013780cf
make concurrency helper more pleasant to read
commit sha d0178b4f99c70d2443f9b76421429d0d23dadc45
Make it platform-specific whether `hard_link` follows symlinks. Also mention that where possible, `hard_link` does not follow symlinks.
push time in 6 days
push eventshepmaster/rust
commit sha cc19df627ea87e199163e0e487a251976ea7897e
revert #75443 update mir validator
commit sha ae4f80b4beb67101708a6bf5646dd159ad33318c
Revert "Revert "resolve: Avoid "self-confirming" import resolutions in one more case"" This reverts commit b20bce8ce54ea9d47c2e3eb0b17cbb6baf916ae2. It retains the test added in that commit as a check-pass test, intended to prevent future (unintentional) regressions.
commit sha 51331e4739ee274ff84e46499fb8641b0d540ca7
Re-enable debug and LLVM assertions Historically we've disabled these assertions on a number of platforms with the goal of speeding up CI. Now, though, having migrated to GitHub actions, CI is already pretty fast, and these debug assertions do bring us some value. This does leave in some debug assertions that are performance-related: macOS currently hovers at just under 2 hours. There are also some other builders which have debug and LLVM assertions disabled: llvm-8, PR builder: In one view, this builder tests our support for older LLVMs. But in reality, a lot of our tests already disable themselves on older LLVMs, and I think our general stance is that we really only support the in-tree LLVM. Plus, we really want CI times on this builder to be really low, as it's run on *every* PR -- that's a lot of CI time. test-various: This disables debug asserts still -- as noted in the Dockerfile, we test code size, and we need debug asserts off for that to work well.
commit sha 3ca882986b31a801820a757dec0a89256804c0a7
Add debug asserts to PR builder This is helpful to catch slightly more bugs before things hit main CI, and doesn't cost too much extra CI time.
commit sha e06785b676bb639fef071feca302432c61fbddcc
improve fixme
commit sha ffe65f825b81485c4babf45c85401d5b29eb5e92
rustc_target: Move `target_c_int_width` from `Target` to `TargetOptions`
commit sha 91533cf10e214f150dd813113e492565bb34f3e0
rustc_target: Move `target_endian` from `Target` to `TargetOptions`
commit sha 74ffb9b4a2846dd44ece0583a869df0ca8581268
rustc_target: Move `target_os` from `Target` to `TargetOptions`
commit sha d5fd31197fe1a4f704186874b67e170ff4029a4c
rustc_target: Move `target_env` from `Target` to `TargetOptions`
commit sha b294cc71a2244fb11dad0b1b22e9f27d4b8fba47
rustc_target: Move `target_vendor` from `Target` to `TargetOptions`
commit sha d41fe05d1ae5622af64289487845adc2132d1b77
rustc_target: Move `linker_flavor` from `Target` to `TargetOptions`
commit sha c0c0597e099a6c6b1f3b47e839a630c5bc97aab9
Update recently added targets
commit sha b2d115f6db5172c961dfeb50de15f35784dbc7c9
Auto merge of #75199 - Mark-Simulacrum:debug-asserts, r=pietroalbini Re-enable debug and LLVM assertions Historically we've disabled these assertions on a number of platforms with the goal of speeding up CI. Now, though, having migrated to GitHub actions, CI is already pretty fast, and these debug assertions do bring us some value. This does leave in some debug assertions that are performance-related: macOS currently hovers at just under 2 hours. There are also some other builders which have debug and LLVM assertions disabled: llvm-8, PR builder: In one view, this builder tests our support for older LLVMs. But in reality, a lot of our tests already disable themselves on older LLVMs, and I think our general stance is that we really only support the in-tree LLVM. Plus, we really want CI times on this builder to be really low, as it's run on *every* PR -- that's a lot of CI time. test-various: This disables debug asserts still -- as noted in the Dockerfile, we test code size, and we need debug asserts off for that to work well. Helps with #59637 -- but doesn't close it, macOS still has asserts off. r? `@pietroalbini`
commit sha 771cc7ffc35b832bf35fecb22860eabb70c91da5
Auto merge of #78784 - Mark-Simulacrum:revert-77421, r=petrochenkov Revert "Revert "resolve: Avoid "self-confirming" import resolutions in one more case"" Specifically, this reverts commit b20bce8ce54ea9d47c2e3eb0b17cbb6baf916ae2 from #77421 to fix #77586. The lang team has decided that for the time being we want to avoid the breakage here (perhaps for a future edition; though almost certainly not the upcoming one), though a future PR may want to add a lint around this case (and perhaps others) which are unlikely to be readable code. r? `@petrochenkov` to confirm this is the right way to fix #77586.
commit sha f2ea2f648e117013b0217f001088ae89e0f163ca
Auto merge of #77729 - petrochenkov:mergetarg, r=Mark-Simulacrum rustc_target: Move some target options from `Target` to `TargetOptions` The only reason for `Target` to `TargetOptions` to be separate structures is that options in `TargetOptions` have reasonable defaults and options in `Target` don't. (Otherwise all the options logically belong to a single `Target` struct.) This PR moves a number of options with reasonable defaults from `Target` to `TargetOptions`, so they no longer needs to be specified explicitly for majority of the targets. The move also allows to inherit the options from `rustc_target/src/spec/*_base.rs` files in a nicer way. I didn't change any specific option values here. The moved options are `target_c_int_width` (defaults to `"32"`), `target_endian` (defaults to `"little"`), `target_os` (defaults to `"none"`), `target_env` (defaults to `""`), `target_vendor` (defaults to `"unknown"`) and `linker_flavor` (defaults to `LinkerFlavor::Gcc`). Next steps (in later PRs): - Find a way to merge `TargetOptions` into `Target` - If not, always access `TargetOptions` fields through `Deref` making it a part of `Target` at least logically (`session.target.target.options.foo` -> `session.target.target.foo`) - ~Eliminate `session::config::Config` and use `Target` instead (`session.target.target.foo` -> `session.target.foo`)~ Done in https://github.com/rust-lang/rust/pull/77943. - Avoid tautologies in option names (`target.target_os` -> `target.os`) - Resolve _ https://github.com/rust-lang/rust/issues/77730 (rustc_target: The differences between `target_os = "none"` and `target_os = "unknown"`, and `target_vendor = "unknown"` and `target_vendor = ""` are unclear) noticed during implementation of this PR.
commit sha 87a0997ef9c0bfad0ba362741afa601d8fb285b8
Auto merge of #78410 - lcnr:revert75443, r=nikomatsakis revert #75443, update mir validator This PR reverts rust-lang#75443 to fix rust-lang#75992 and instead uses rust-lang#75419 to fix rust-lang#75313. Adapts rust-lang#75419 to correctly deal with unevaluated constants as otherwise some `feature(const_evaluatable_checked)` tests would ICE. Note that rust-lang#72793 was also fixed by rust-lang#75443, but as that issue only concerns `feature(type_alias_impl_trait)` I deleted that test case for now and would reopen that issue. rust-lang#75443 may have also allowed some other code to now successfully compile which would make this revert a breaking change after 2 stable versions, but I hope that this is a purely theoretical concern. See https://rust-lang.zulipchat.com/#narrow/stream/182449-t-compiler.2Fhelp/topic/generator.20upvars/near/214617274 for more reasoning about this. r? `@nikomatsakis` `@eddyb` `@RalfJung`
push time in 16 days
push eventshepmaster/rust
commit sha 76daca2791f3deeee925e449d7db51795f55121d
Add #[inline] to some core::str functions. Almost all these functions already had #[inline]. These were missing.
commit sha cc850ecba0641f0ec56507ee656ad9a301705c83
Add #[inline] to {&str, &mut str}::default.
commit sha c4ae6c2bb95551afed4b87346cdf4ad4e4ba052c
Add comment
commit sha 67bc11bd0480b5657c8c8db233e55f9b16ed664a
Add more infomation about LintStore registration Backstory: I somehow missed the fact that I needed to register a lint pass in order for it to run, and I spent some time confused until I figured it out. So I wanted to make it clear that a missing `register_(early|late)_pass` call is a likely cause of a lint not running.
commit sha 114cb218f3ab2a709e3017c380790dd6e407132c
Remove an extra blank line in doc examples
commit sha be136b27126cfb614eff3c0b032dcd2b3837db26
Merge remote-tracking branch 'upstream/master' into sync-from-rust
commit sha 3d3507230c62e94dcef2cea8c25c90d1d171e329
Auto merge of #6195 - giraffate:sync-from-rust, r=ebroto Rustup I followed these steps: <https://github.com/rust-lang/rust-clippy/blob/master/CONTRIBUTING.md#fixing-build-failures-caused-by-rust>. changelog: none
commit sha ec23db9496807f6c962b74fe0d6bf15be6c6d35b
Add linter for a single element for loop Signed-off-by: Patrick José Pereira <[email protected]>
commit sha ba1ca19c3bec20401a4cb13e5186c4c5952e94cc
tests: if_same_then_else2: Ignore single_element_loop lint Signed-off-by: Patrick José Pereira <[email protected]>
commit sha 74530adcba45edbd99bb5a96b45fe2c8e12a31aa
Auto merge of #6166 - achris:master, r=flip1995 Suggest a compatible shell for setup-toolchain.sh setup-toolchain.sh uses "[[" which is a bash builtin, but the guide suggests running it with sh. On Ubuntu, /bin/sh points to dash and running the script fails. --- *Please keep the line below* changelog: none
commit sha 13a5067061c14875bf1deda44a4740c08e872eb9
Unignore test
commit sha 0558e6eb9337960a1415e037ae7a44e3aa947479
bootstrap: fall back to auto-detected CXX This allows us to use the C++ compiler configured via `CXX_target_triple` env vars
commit sha 77a7ccf869db577c0d7262965c0ecdd1f50a49b8
bootstrap: configure native toolchain for run-make This allows moving a lot of run-make-fulldeps tests to just run-make tests, and allows running those on target-only platforms
commit sha e36de6b2a1acc2826482f44a46b90678baccaaff
Move issue-36710 test to run-make Somewhat hacky to reuse `tools.mk` like this, we should probably migrate most of them now
commit sha a67160494cb9305e72aae5b367d9187f2f37e572
Ignore test on WASM
commit sha d7c7649f5b4688e73046d45293e4d046ade59135
ignore-thumb
commit sha 60594b1f0fd0fa69959e4fe56a61c01031916fe2
Ignore on 32-bit targets
commit sha 16b5f37b5a23f475d0d94efea764c57e4572f63f
Split `eq_op` ui tests to avoid file limit error in CI
commit sha b62b352f4779072c07c110a63fd83afa9508b9e9
Check for exhaustion in RangeInclusive::contains When a range has finished iteration, `is_empty` returns true, so it should also be the case that `contains` returns false.
commit sha eaffd0e41837dd952d0854a2f2aea35cccbb6319
Auto merge of #6167 - ThibsG:IdenticalArgumentsAssertEq3574, r=ebroto Identical arguments on assert macro family Lint when identical args are used on `assert_eq!`, `debug_assert_eq!`, `assert_ne!` and `debug_assert_ne!` macros. Added to the lint `eq_op`. Common functions added to `utils/higher.rs` Fixes: #3574 Fixes: #4694 changelog: Lint on identical args when calling `assert_eq!`, `debug_assert_eq!`, `assert_ne!` and `debug_assert_ne!` macros
push time in 16 days
PR opened dropbox/fast_rsync
The resulting code is a little ugly, but not too bad.
This allows the crate to compile on stable.
pr created time in 21 days
push eventReadyTalk/avian
commit sha 0871979b298add320ca63f65060acb7532c8a0dd
Fix integer overflow leading to out-of-bounds read/write
push time in a month
startedviridia/vortex
started time in a month
startedviridia/sapling
started time in a month
push eventshepmaster/rust
commit sha 0a91755ff4b6899e1c0675c48b4652e890ce63aa
Properly define va_arg and va_list for aarch64-apple-darwin From [Apple][]: > Because of these changes, the type `va_list` is an alias for `char*`, > and not for the struct type in the generic procedure call standard. With this change `/x.py test --stage 1 src/test/ui/abi/variadic-ffi` passes. Fixes #78092 [Apple]: https://developer.apple.com/documentation/xcode/writing_arm64_code_for_apple_platforms
push time in a month
push eventshepmaster/rust
commit sha c6ab758e54bd509f75df7a21fd72aa740ac5a4b0
Switch from tuple matching to match guards
commit sha d6bfde4bc10d7ef336b84613a0e926c35bc288ef
Properly define va_arg and va_list for aarch64-apple-darwin From [Apple][]: > Because of these changes, the type `va_list` is an alias for `char*`, > and not for the struct type in the generic procedure call standard. With this change `/x.py test --stage 1 src/test/ui/abi/variadic-ffi` passes. Fixes #78092 [Apple]: https://developer.apple.com/documentation/xcode/writing_arm64_code_for_apple_platforms
push time in a month
push eventshepmaster/rust
commit sha fd22e87afc9082522bc7b52e32d25d43c64594e6
fix flag computation for `ExistentialPredicate::Projection`
commit sha 7652b4b1d9cec0ad22f529a4335d05f7d7792521
guard against `skip_binder` errors during FlagComputation
commit sha a7bd6c449aef07dc8daa889f4ddbdda326593e32
Link to "Contributing to Rust" rather than "Getting Started". Change to link to "Contributing to Rust" chapter of `rustc` Dev Guide, primarily on the basis that the GitHub "first contribution" Issue "pop-up" says "Be sure to review the [contributing guidelines] and [code of conduct]" and links to this file. When/if the guide/"Getting Started" section gets revised to not be `rustc`-specific the linked section can be changed. In the meantime this prevents leading first time contributors into a confusing cul de sac.
commit sha 81edbbc2bfacd29558a5020990d49fc07ed80ac7
Implement TryFrom between NonZero types.
commit sha 77e6c56ab6f108fdbb8acbd176497be9f074af9a
Unify `&mut` and `&raw mut` const-checking errors
commit sha c1494d60dbad39c218e7b0825bfe590cc22bf2fa
Bless tests
commit sha 64839ee00ab4076d797901ddea55f2613c5b75b5
Add Pin::new_static.
commit sha 390883e888c580d054ab4a2584c851aba50865e9
Make Pin::new_static const.
commit sha bd135674814d74ca6fca3ab79d778ecaaeb02cf5
Allow setting up git hooks from other worktrees
commit sha 0ec3ea9e697ea9c2ce225ba0b9f3715434fc773e
const keyword: brief paragraph on 'const fn'
commit sha c8405d2251ce78651f591ed8a2189c41593f5110
fix markdown reference Co-authored-by: Dariusz Niedoba <[email protected]>
commit sha 39b0e7928579c4ce3a42e849695f9380b7869d62
Remove generic argument from `QueryConfig`.
commit sha 104c0f0194177442ff16cf14907a96d2f8d200dd
Rename Pin::new_static to Pin::static_ref.
commit sha 2c71f682d74d13ae6673dc701a9bb3a0562f57c0
Add Pin::static_mut.
commit sha 0c32e811577fbf2ff46a607897f9ea7b6b95b364
Fixing escaping to ensure generation of welformed json.
commit sha f83446b836900ce9afbaa0816a5b4feda654b51e
Reword safety guarantee of Pin::static_{ref,mut}. Co-authored-by: Peter Todd <[email protected]>
commit sha a93f58f5e6c9e4e1fbc076d966a9e1e853ea06fd
Join map operators Signed-off-by: wcampbell <[email protected]>
commit sha 964a5ac962d32c280d036df42b2e747809939cc4
Use is_ok() instead of empty Ok(_) Signed-off-by: wcampbell <[email protected]>
commit sha abfbd1bd719bd1440132ead24ec64c0acd293f41
Avoid extraneous space between visibility kw and ident for statics Today, given a static like `static mut FOO: usize = 1`, rustdoc would emit `static mut FOO: usize = 1`, as it emits both the mutability kw with a space and reserves a space after the mutability kw. This patch fixes that misformatting. This patch also adds some tests for emit of other statics, as I could not find an existing test devoted to statics.
commit sha e60072f5c65c619263d137daf9afab9c6cb94c8e
fixup! Avoid extraneous space between visibility kw and ident for statics
push time in a month
push eventshepmaster/rust
commit sha fd22e87afc9082522bc7b52e32d25d43c64594e6
fix flag computation for `ExistentialPredicate::Projection`
commit sha 7652b4b1d9cec0ad22f529a4335d05f7d7792521
guard against `skip_binder` errors during FlagComputation
commit sha a7bd6c449aef07dc8daa889f4ddbdda326593e32
Link to "Contributing to Rust" rather than "Getting Started". Change to link to "Contributing to Rust" chapter of `rustc` Dev Guide, primarily on the basis that the GitHub "first contribution" Issue "pop-up" says "Be sure to review the [contributing guidelines] and [code of conduct]" and links to this file. When/if the guide/"Getting Started" section gets revised to not be `rustc`-specific the linked section can be changed. In the meantime this prevents leading first time contributors into a confusing cul de sac.
commit sha 81edbbc2bfacd29558a5020990d49fc07ed80ac7
Implement TryFrom between NonZero types.
commit sha 77e6c56ab6f108fdbb8acbd176497be9f074af9a
Unify `&mut` and `&raw mut` const-checking errors
commit sha c1494d60dbad39c218e7b0825bfe590cc22bf2fa
Bless tests
commit sha 64839ee00ab4076d797901ddea55f2613c5b75b5
Add Pin::new_static.
commit sha 390883e888c580d054ab4a2584c851aba50865e9
Make Pin::new_static const.
commit sha bd135674814d74ca6fca3ab79d778ecaaeb02cf5
Allow setting up git hooks from other worktrees
commit sha 0ec3ea9e697ea9c2ce225ba0b9f3715434fc773e
const keyword: brief paragraph on 'const fn'
commit sha c8405d2251ce78651f591ed8a2189c41593f5110
fix markdown reference Co-authored-by: Dariusz Niedoba <[email protected]>
commit sha 39b0e7928579c4ce3a42e849695f9380b7869d62
Remove generic argument from `QueryConfig`.
commit sha 104c0f0194177442ff16cf14907a96d2f8d200dd
Rename Pin::new_static to Pin::static_ref.
commit sha 2c71f682d74d13ae6673dc701a9bb3a0562f57c0
Add Pin::static_mut.
commit sha 0c32e811577fbf2ff46a607897f9ea7b6b95b364
Fixing escaping to ensure generation of welformed json.
commit sha f83446b836900ce9afbaa0816a5b4feda654b51e
Reword safety guarantee of Pin::static_{ref,mut}. Co-authored-by: Peter Todd <[email protected]>
commit sha a93f58f5e6c9e4e1fbc076d966a9e1e853ea06fd
Join map operators Signed-off-by: wcampbell <[email protected]>
commit sha 964a5ac962d32c280d036df42b2e747809939cc4
Use is_ok() instead of empty Ok(_) Signed-off-by: wcampbell <[email protected]>
commit sha abfbd1bd719bd1440132ead24ec64c0acd293f41
Avoid extraneous space between visibility kw and ident for statics Today, given a static like `static mut FOO: usize = 1`, rustdoc would emit `static mut FOO: usize = 1`, as it emits both the mutability kw with a space and reserves a space after the mutability kw. This patch fixes that misformatting. This patch also adds some tests for emit of other statics, as I could not find an existing test devoted to statics.
commit sha e60072f5c65c619263d137daf9afab9c6cb94c8e
fixup! Avoid extraneous space between visibility kw and ident for statics
push time in a month
push eventshepmaster/rust
commit sha d8aaf3d25f43ac2ac6930082e750049e2dbf3a86
Properly define va_arg and va_list for aarch64-apple-darwin From [Apple][]: > Because of these changes, the type `va_list` is an alias for `char*`, > and not for the struct type in the generic procedure call standard. With this change `/x.py test --stage 1 src/test/ui/abi/variadic-ffi` passes. Fixes #78092 [Apple]: https://developer.apple.com/documentation/xcode/writing_arm64_code_for_apple_platforms
push time in a month
push eventshepmaster/rust
commit sha e023158145ece18176a2e93420600ccda0d0bc58
Permit uninhabited enums to cast into ints This essentially reverts part of #6204.
commit sha 990a39596cf3b33e550f2045f78a62970f8d78f8
Prevent ICE on uninhabited MIR interpretation
commit sha a02014280586b53997622c501db00398376967a8
Refactor io/buffered.rs into submodules
commit sha 96229f02402e82914ec6100b28ad2cbdd273a0d4
move buffered.rs to mod.rs
commit sha 6d75cdfc9ed9e6987bd23add6cf3954d2499dce2
Added updated compiler diagnostic
commit sha da700cba08a2b194d19e63d3c51ebadce96fe46b
Stabilize move_ref_pattern
commit sha afb9eeb1b9ea16ca65e38673a0ef3e7be81d7252
Disabled error `E0007` from rustc_error_codes
commit sha 05c9c0ee5dcd935f518db151bee2dc88380fb92f
Modify executable checking to be more universal This uses a dummy file to check if the filesystem being used supports the executable bit in general.
commit sha c4280af8285c61b367a87c8f6eef9876011a8150
Retry fix error reporting suggestions
commit sha 1ff7da6551a7cdf6ace2a9d00e92bbab550334ee
Move `slice::check_range` to `RangeBounds`
commit sha 1095dcab96d524e700b11edf366d45a0fd173fa0
Fix links
commit sha eb63168e007058dad4af758faf1dca449c049777
Fix doctests
commit sha f055b0bb0847ecf08fe452a270faae8324b55b05
Rename method to `assert_len`
commit sha 549f861f7d53811521cf929cf58fb6828a2a88d9
Use correct article in help message for conversion or cast Before it always used `an`; now it uses the correct article for the type.
commit sha 094f14c554c3a1f103a5d6778d4b4e131c297f11
Add article after "to" Also added missing backtick in "you can cast" message.
commit sha 8a6831a7fd3fc624643b50f494212e0ceaad3c28
Say "doesn't" instead of "wouldn't" in convert message
commit sha 13dfbb64d313137b7d3c33067910e90f27bc6345
Suggest imports of unresolved macros
commit sha 479298e05e8177b171c6d6bcd35fc7553b424bee
Re-run tests with --bless
commit sha ea7cf6106864ce7929eb9f3cfe580f05ee418ac8
Don't suggest macros that out of scope
commit sha 0b923d3ca0b7f5a1a611564ee48c1e92f896d79e
add `str::{Split,RSplit}::as_str` methods This commit introduses 2 methods under "str_split_as_str" gate with common signature of `&Split<'a, _> -> &'a str'`. Both of them work like `Chars::as_str` - return unyield part of the inner string.
push time in a month
created tagdropbox/fast_rsync
An optimized implementation of librsync in pure Rust.
created time in a month
push eventdropbox/fast_rsync
commit sha e7b16376be5b891ecca6d44bd1f02ec2b3b20273
(cargo-release) version 0.1.3
commit sha 63004bd11d4d30981229811210bd005332b60d89
(cargo-release) start next development iteration 0.1.4-alpha.0
push time in a month