profile
viewpoint
Valentin Lazureanu Lezzz Romania

Lezzz/rust 1

Empowering everyone to build reliable and efficient software.

Lezzz/caesar_cipher 0

Simple Caesar Cipher in Ruby

Lezzz/etch-a-sketch 0

Online Sketchpad.

Lezzz/meghna-hugo 0

Meghna Hugo Template

Lezzz/museum_of_candy 0

A Bootstrap Presentation Website for a possible candy store.

Lezzz/my_first_rails_app 0

First Rails app

delete branch Lezzz/rust

delete branch : adjust-librustc-ast

delete time in 2 months

delete branch Lezzz/rust

delete branch : rename-tables

delete time in 2 months

delete branch Lezzz/rust

delete branch : rename-hair

delete time in 2 months

push eventLezzz/rust

Aaron Hill

commit sha ac9dfc3e7785c9bba96ebac4fd51726189e1bf91

Normalize opaque types when converting `ParamEnv` to `Reveal::All` Fixes #65918

view details

Aaron Hill

commit sha 117a60e1f5045e317d3f76ce60be28d18c694608

Erase regions in try_eval_bits

view details

Aaron Hill

commit sha 90aee14eb95ac0b9ddb7cf5db6d003155e94800c

Skip computing param_env and size if not needed

view details

Aaron Hill

commit sha 5e2e927e0107916b825b164c82be44877ac6ab54

Fix rebase fallout

view details

Alan Somers

commit sha 013e1a6e9f73125734cb919d9b6220b3a4710d67

Enable the profiler on FreeBSD FreeBSD has been doing this in our own package builds for two months now. https://svnweb.freebsd.org/ports?view=revision&revision=535771

view details

Alex Crichton

commit sha 06d565c967bfb7c6ff52a991bbe47b4a2a25de3e

std: Switch from libbacktrace to gimli This commit is a proof-of-concept for switching the standard library's backtrace symbolication mechanism on most platforms from libbacktrace to gimli. The standard library's support for `RUST_BACKTRACE=1` requires in-process parsing of object files and DWARF debug information to interpret it and print the filename/line number of stack frames as part of a backtrace. Historically this support in the standard library has come from a library called "libbacktrace". The libbacktrace library seems to have been extracted from gcc at some point and is written in C. We've had a lot of issues with libbacktrace over time, unfortunately, though. The library does not appear to be actively maintained since we've had patches sit for months-to-years without comments. We have discovered a good number of soundness issues with the library itself, both when parsing valid DWARF as well as invalid DWARF. This is enough of an issue that the libs team has previously decided that we cannot feed untrusted inputs to libbacktrace. This also doesn't take into account the portability of libbacktrace which has been difficult to manage and maintain over time. While possible there are lots of exceptions and it's the main C dependency of the standard library right now. For years it's been the desire to switch over to a Rust-based solution for symbolicating backtraces. It's been assumed that we'll be using the Gimli family of crates for this purpose, which are targeted at safely and efficiently parsing DWARF debug information. I've been working recently to shore up the Gimli support in the `backtrace` crate. As of a few weeks ago the `backtrace` crate, by default, uses Gimli when loaded from crates.io. This transition has gone well enough that I figured it was time to start talking seriously about this change to the standard library. This commit is a preview of what's probably the best way to integrate the `backtrace` crate into the standard library with the Gimli feature turned on. While today it's used as a crates.io dependency, this commit switches the `backtrace` crate to a submodule of this repository which will need to be updated manually. This is not done lightly, but is thought to be the best solution. The primary reason for this is that the `backtrace` crate needs to do some pretty nontrivial filesystem interactions to locate debug information. Working without `std::fs` is not an option, and while it might be possible to do some sort of trait-based solution when prototyped it was found to be too unergonomic. Using a submodule allows the `backtrace` crate to build as a submodule of the `std` crate itself, enabling it to use `std::fs` and such. Otherwise this adds new dependencies to the standard library. This step requires extra attention because this means that these crates are now going to be included with all Rust programs by default. It's important to note, however, that we're already shipping libbacktrace with all Rust programs by default and it has a bunch of C code implementing all of this internally anyway, so we're basically already switching already-shipping functionality to Rust from C. * `object` - this crate is used to parse object file headers and contents. Very low-level support is used from this crate and almost all of it is disabled. Largely we're just using struct definitions as well as convenience methods internally to read bytes and such. * `addr2line` - this is the main meat of the implementation for symbolication. This crate depends on `gimli` for DWARF parsing and then provides interfaces needed by the `backtrace` crate to turn an address into a filename / line number. This crate is actually pretty small (fits in a single file almost!) and mirrors most of what `dwarf.c` does for libbacktrace. * `miniz_oxide` - the libbacktrace crate transparently handles compressed debug information which is compressed with zlib. This crate is used to decompress compressed debug sections. * `gimli` - not actually used directly, but a dependency of `addr2line`. * `adler32`- not used directly either, but a dependency of `miniz_oxide`. The goal of this change is to improve the safety of backtrace symbolication in the standard library, especially in the face of possibly malformed DWARF debug information. Even to this day we're still seeing segfaults in libbacktrace which could possibly become security vulnerabilities. This change should almost entirely eliminate this possibility whilc also paving the way forward to adding more features like split debug information. Some references for those interested are: * Original addition of libbacktrace - #12602 * OOM with libbacktrace - #24231 * Backtrace failure due to use of uninitialized value - #28447 * Possibility to feed untrusted data to libbacktrace - #21889 * Soundness fix for libbacktrace - #33729 * Crash in libbacktrace - #39468 * Support for macOS, never merged - ianlancetaylor/libbacktrace#2 * Performance issues with libbacktrace - #29293, #37477 * Update procedure is quite complicated due to how many patches we need to carry - #50955 * Libbacktrace doesn't work on MinGW with dynamic libs - #71060 * Segfault in libbacktrace on macOS - #71397 Switching to Rust will not make us immune to all of these issues. The crashes are expected to go away, but correctness and performance may still have bugs arise. The gimli and `backtrace` crates, however, are actively maintained unlike libbacktrace, so this should enable us to at least efficiently apply fixes as situations come up.

view details

Manish Goregaokar

commit sha abaf38ccb08d64a2a2c6b5d66dca2b58c2427664

Rename intra_doc_link_resolution_failure -> intra_doc_link_resolution_failures

view details

Manish Goregaokar

commit sha 48de8ac0416853aaf76fcbe721efe9f11e27bd9d

Rename usage of intra_doc_link_resolution_failure

view details

Manish Goregaokar

commit sha da0b10c4fb2ff230fd68e3096c467da5dd82e89e

Register renamed lint

view details

Manish Goregaokar

commit sha 4df76f0f90fc0aa4cb3ed4c2c812c6f505f3e21e

Rename to intra_doc_resolution_failures

view details

Manish Goregaokar

commit sha 7b7b5a7a129a640e4c652fbe91dd4113b0b5e06c

Rename in library

view details

Manish Goregaokar

commit sha 522ef2e9811139e80e39cd1d5da2514cf9b7a8b4

Remove deny for intra doc link failures from library code, it's no longer necessary

view details

Manish Goregaokar

commit sha bcb2813e01313f78f580e0e7af263c27cc77a825

Update uitest expectations

view details

Manish Goregaokar

commit sha 8fe438e632c0fe6a6d99f5096e21d9ab5d16fe3c

intra_doc_resolution_failures -> broken_intra_doc_links

view details

Manish Goregaokar

commit sha e25a67fa6cbfacea80f5579149299f842775be79

Rename the lint again

view details

Manish Goregaokar

commit sha c17eb566c20bb4c98a1e74f7f0461483ff175310

Fix uitests

view details

Joseph Ryan

commit sha 48c6f05662b0bf58cce0e867e60c2d86b5e6fcfb

Update driver to add json backend

view details

Rich Kadel

commit sha 34b26d6a77c45776cbbef182b4c1b0b96ac326fe

Rust function-level coverage now works on external crates Fixed a known issue in the coverage map where some regions had nonsensical source code locations. External crate functions are already included in their own coverage maps, per library, and don't need to also be added to the importing crate's coverage map. (In fact, their source start and end byte positions are not relevant to the importing crate's SourceMap.) The fix was to simply skip trying to add imported coverage info to the coverage map if the instrumented function is not "local". The injected counters are still relevant, however, and the LLVM `instrprof.increment` intrinsic call parameters will map those counters to the external crates' coverage maps, when generating runtime coverage data.

view details

Dylan MacKenzie

commit sha fc2c1f8ddc9a460c558741ae44b894faf3967f7c

Make `Option::unwrap` unstably const `Result::unwrap` is not eligible becuase it formats the contents of the `Err` variant. `unwrap_or`, `unwrap_or_else` and friends are not eligible because they drop things or invoke closures.

view details

Dylan MacKenzie

commit sha 96c84ac3cbc4f2c81580893dacf263d00306649c

Test `Option::unwrap` in a const context

view details

push time in 2 months

push eventLezzz/rust

Guillaume Gomez

commit sha 1d2e3fff69b654c3dfd6a810e193db29bb1868fa

Clean up E0730 explanation

view details

Guillaume Gomez

commit sha f22a34e84d4dba9b17bb3e68051ee82bd85f3c94

Clean up E0734 explanation

view details

Michal 'vorner' Vaner

commit sha ad6d63ef01e37a1a05acdba50985b01d178d7c11

Don't use "weak count" around Weak::from_raw_ptr As `Rc/Arc::weak_count` returns 0 when having no strong counts, this could be confusing and it's better to avoid using that completely. Closes #73840.

view details

David Sonder

commit sha b5d143b126cd73c873fc8feff7dee0a0b077cc84

Enable docs on dist-x86_64-musl Add the rust-docs component to toolchain x86_64-unknown-linux-musl, which allows people using rustup on their musl-based linux distribution to download the rust-docs.

view details

Lzu Tao

commit sha 0374006d79114824d8eec020a9d771ca8cf712ff

Avoid bool-like naming

view details

Guillaume Gomez

commit sha 759de11f534b940f090ff94cf1829935c1eb4e7d

Clean up E0740 explanation

view details

Gary Guo

commit sha 8046fea62263d50fc196ce07ccdc4534af321441

Improve diagnostics when constant pattern is too generic

view details

Gary Guo

commit sha 4e963d58c7d94270697c2765f23993e40757292f

Fix ui tests

view details

Guillaume Gomez

commit sha 89e4fe33130a17888a2add6baadd850653263242

Improve E0730 explanation

view details

Alex Crichton

commit sha cd8bdb5eb9a7440fa64500218f43b04429e64fc1

rustc: Ignore fs::canonicalize errors in metadata This commit updates the metadata location logic to ignore errors when calling `fs::canonicalize`. Canonicalization was added historically so multiple `-L` paths to the same directory don't print errors about multiple candidates (since rustc can deduplicate same-named paths), but canonicalization doesn't work on all filesystems. Cargo, for example, always uses this sort of fallback where it will opportunitistically try to canonicalize but fall back to using the input path if it otherwise doesn't work. If rustc is run on a filesystem that doesn't support canonicalization then the effect of this change will be that `-L` paths which logically point to the same directory will cause errors, but that's a rare enough occurrence it shouldn't cause much issue in practice. Otherwise rustc doesn't work at all today on those sorts of filesystem where canonicalization isn't supported!

view details

Mark Rousskov

commit sha e1e01f72a5e5f4ebcf455a2df72781aa1cbb2016

1.45.1 release (cherry picked from commit 9e5fb40807f97fe47d2eaca99daeb1f1f6ff07a7)

view details

Mark Rousskov

commit sha 19d191bb02d1566096493a26904826d4e81beeda

Update release notes (cherry picked from commit 32166ab1ebec2e5e5454221f0d3238c21382de9f)

view details

Manish Goregaokar

commit sha 7e86c8eccbd032068cc474611e41a13ac6d0bbd7

Rollup merge of #74751 - GuillaumeGomez:cleanup-e0730, r=jyn514 Clean up E0730 explanation r? @Dylan-DPC

view details

Manish Goregaokar

commit sha 46379687ac0bf3c553c9c2f30fb8225210208a15

Rollup merge of #74782 - vorner:weak-into-raw-cnt-doc, r=dtolnay Don't use "weak count" around Weak::from_raw_ptr As `Rc/Arc::weak_count` returns 0 when having no strong counts, this could be confusing and it's better to avoid using that completely. Closes #73840.

view details

Manish Goregaokar

commit sha 172b3a713aaaa788f236a286d963d2129104a400

Rollup merge of #74835 - GuillaumeGomez:cleanup-e0734, r=jyn514 Clean up E0734 explanation r? @Dylan-DPC

view details

Manish Goregaokar

commit sha 8892785c8e0aed3cc8a30d14deda24bfc04a2908

Rollup merge of #74871 - etherealist:musl_doc, r=Mark-Simulacrum Enable docs on dist-x86_64-musl Add the `rust-docs` component to toolchain `x86_64-unknown-linux-musl`, which allows people using rustup on their musl-based linux distribution to download the rust-docs. `--disable-docs` is based on the assumption that `x86_64-unknown-linux-musl` is only a cross-compile target. I have tested that the docs are built. I assume the build-system will automatically detect the docs and create a `rust-docs` component. I will [monitor](https://rust-lang.github.io/rustup-components-history/x86_64-unknown-linux-musl.html) the components and create a follow-up PR, if the docs aren't published. See also #70619, where we enabled `rust-lld` to enable the wasm-workflow on musl-based linux distributions.

view details

Manish Goregaokar

commit sha e823af6015cbd9b9f6d97a84e86adada3de82a4d

Rollup merge of #74905 - lzutao:listed, r=jyn514 Avoid bool-like naming Lost in https://github.com/rust-lang/rust/pull/74127#discussion_r453143504

view details

Manish Goregaokar

commit sha 2c6c764d9a37b0954afe8d005c8566dcbf12380d

Rollup merge of #74907 - GuillaumeGomez:cleanup-e0740, r=pickfire Clean up E0740 explanation r? @Dylan-DPC

view details

Manish Goregaokar

commit sha 0a45b1303cafc39458ffd3944dcf74c8b4200df6

Rollup merge of #74915 - alexcrichton:allow-failing-canonicalize, r=Mark-Simulacrum rustc: Ignore fs::canonicalize errors in metadata This commit updates the metadata location logic to ignore errors when calling `fs::canonicalize`. Canonicalization was added historically so multiple `-L` paths to the same directory don't print errors about multiple candidates (since rustc can deduplicate same-named paths), but canonicalization doesn't work on all filesystems. Cargo, for example, always uses this sort of fallback where it will opportunitistically try to canonicalize but fall back to using the input path if it otherwise doesn't work. If rustc is run on a filesystem that doesn't support canonicalization then the effect of this change will be that `-L` paths which logically point to the same directory will cause errors, but that's a rare enough occurrence it shouldn't cause much issue in practice. Otherwise rustc doesn't work at all today on those sorts of filesystem where canonicalization isn't supported!

view details

Manish Goregaokar

commit sha b0d426165f871f4e50d2fae47e6a5e9c54d1ba12

Rollup merge of #74934 - nbdd0121:issue-73976, r=ecstatic-morse Improve diagnostics when constant pattern is too generic This PR is a follow-up to PR #74538 and issue #73976 When constants queries Layout, TypeId or type_name of a generic parameter, instead of emitting `could not evaluate constant pattern`, we will instead emit a more detailed message `constant pattern depends on a generic parameter`.

view details

push time in 2 months

push eventLezzz/rust

flip1995

commit sha f7acea2683c6124854bfe20e7127e4dfba344d3e

Register redundant_field_names and non_expressive_names as early passes

view details

flip1995

commit sha 485229c4a3d6a2fbe40f5a6976a33144a27497c6

Fix fallout in redundant_field_names

view details

flip1995

commit sha efd3dcff97f67f376e354c047133ce9044c52991

Fix fallout in similar_names

view details

Eduardo Broto

commit sha bb37a0f948b02e6434dbe3ea615960052d37f784

Avoid triggering similar names on code from expansion

view details

Alexis Bourget

commit sha 2853448426ce76926baa7e6e6173c15228e4951a

Document the ref keyword

view details

Stefan Lankes

commit sha 6813c1c69baf870a479c70e23ad0550d1d9aa9be

revise RwLock, which is derived from the wasm implementation - increasing the readability of `Condvar` - simplify the interface to the libos HermitCore

view details

Stefan Lankes

commit sha 3acc3ef10d2099a4b3118e8c705b36f4bbaf6f64

minor changes to pass the format check

view details

Stefan Lankes

commit sha beb1b1fa5b1047c7caf8a1d499725df3c1ad8cad

reorder crates to pass the format check

view details

Stefan Lankes

commit sha f9c609164251abc136eb9bda55c92cb99adb5c86

remove some compiler warnings

view details

Trevor Spiteri

commit sha 6dfe144bdd4413ac55cbb2ad2edfb1daa0c4bf15

stabilize const_nonzero_int_methods

view details

Trevor Spiteri

commit sha 9739b512a892628534e730ffcd9756b3218c8de8

stabilize some const_checked_int_methods

view details

Trevor Spiteri

commit sha c1c674c2dbfe3f6dc47d11368c1b5ee4ab008799

stabilize const_saturating_int_methods

view details

Trevor Spiteri

commit sha 056d925167318636fcf975c8ffb81efebdc9bca3

stabilize const_int_sign

view details

Trevor Spiteri

commit sha 2a84e313df095fd0e81b9348b68bd9b1d1caa551

stabilize const_ascii_ctype_on_intrinsics

view details

Adam Perry

commit sha d275739c09f266479d6db388cbf55ba6ca791b9d

Derive common traits for panic::Location. Add documentation about the host/target behavior of Location::file.

view details

Jamie Cunliffe

commit sha fc52b47e8013da325fc0a0f5d3897143243ba206

va_args implementation for AAPCS. Implement the va args in codegen for AAPCS, this will be used as the default va_args implementation for AArch64 rather than the va_args llvm-ir as it currently is. Copyright (c) 2020, Arm Limited.

view details

Alexis Bourget

commit sha 837a761b398a6ff6a97f7f61e390dae9efbeab79

Document the where keyword

view details

Andrey Zgarbul

commit sha 7d4a92d4f8dc03409984695d78893fffdd3ff1f9

remove LengthAtMost32 on AsRef/Borrow impl for array

view details

Roman Proskuryakov

commit sha eff62069ad602090e8d27b83cffd9e77479ed4be

Remove the usage of the LengthAtMost32 trait

view details

Roman Proskuryakov

commit sha 4ad40a8737ab4ffaf6352ec4560fd86cb0b4ade8

Remove LengthAtMost32

view details

push time in 2 months

PR opened rust-lang/rust

Rename HAIR to THIR (Typed HIR).

r? @nikomatsakis

+128 -121

0 comment

36 changed files

pr created time in 2 months

push eventLezzz/rust

Valentin Lazureanu

commit sha 3c328b5ec26863eec95fbbe25329ee3defec00e1

Rename HAIR to THIR (Typed HIR).

view details

push time in 2 months

push eventLezzz/rust

Valentin Lazureanu

commit sha 0d09bb3b55e0f66315cd19d2db50d6c4d6a6c8f7

Rename HAIR to THIR (Typed HIR).

view details

push time in 2 months

create barnchLezzz/rust

branch : rename-hair

created branch time in 2 months

delete branch Lezzz/rust

delete branch : rename-typeck

delete time in 2 months

push eventLezzz/rust

Mohsen Zohrevandi

commit sha c4b02659c16d2ad0ac36d2c8602edd002e559f7a

Enable some timeouts in SGX platform This would partially resolve https://github.com/fortanix/rust-sgx/issues/31

view details

Mohsen Zohrevandi

commit sha d7dc64bdfea4fbf8974774800ab51e04eaa4f082

Handle spurious wakeups in wait_timeout_sgx

view details

Mohsen Zohrevandi

commit sha c5d1fcd2309b6903fed82aba6e0fdc2fa85bc874

Allow more ui tests for SGX

view details

Mohsen Zohrevandi

commit sha 3442d23c1a12f1f01a0e07b6bec72b58998f49ef

Improve wait_timeout_sgx, simplify usercalls::wait

view details

Alex Crichton

commit sha fde8d11ca12e83fe2b07a536956f4a2725b24485

Don't pollute docs/suggestions with libstd deps Currently dependency crates of the standard library can sometimes leak into error messages such as when traits to import are suggested. Additionally they can leak into documentation such as in the list of "all traits implemented by `u32`". The dependencies of the standard library, however, are intended to be private. The dependencies of the standard library can't actually be stabl-y imported nor is the documentation that relevant since you can't import them on stable either. This commit updates both the compiler and rustdoc to ignore unstable traits in these two scenarios. Specifically the suggestion for traits to import ignore unstable traits, and similarly the list of traits implemented by a type excludes unstable traits. This commit is extracted from #73441 where the addition of some new dependencies to the standard library was showed to leak into various error messages and documentation. The intention here is to go ahead and land these changes ahead of that since it will likely take some time to land.

view details

Guillaume Gomez

commit sha 99c15133638c42253592a9bbe705ff215c9dd563

Small cleanup for E0705 explanation

view details

joacar01

commit sha 582071c1ebd5ec19ded8648223e9108b5ce65d85

Ignoring test case: [codegen] repr-transparent-aggregates-1.rs for aarch64 Copyright (c) 2020, Arm Limited.

view details

Mohsen Zohrevandi

commit sha c457b67af394c37826f75d73cca10319ee96b910

Remove unnecessary check in SGX wait usercall

view details

Guillaume Gomez

commit sha 69d5fc1a9f89c80dd9e16a43dff58f320b373630

Clean up E0710 explanation

view details

Eric Huss

commit sha 9b6b400084fe617e2549d539963294a9ea178c46

Remove some `ignore-stage1` annotations.

view details

Andy Russell

commit sha 95bf7b7dacca320d0965e3f9052ecbb9c4fc59bd

add regression test for #61216 Fixes #61216.

view details

Yuki Okushi

commit sha 85072e330394440776ace5ae612e3ced32ef6348

Update reference to CONTRIBUTING.md

view details

Guillaume Gomez

commit sha b0884c098bc3704f7ec9381ac1670eb923845127

Move #[doc(alias)] check in rustc

view details

Eric Huss

commit sha 24abe1646e24caca79cd649f71cd4806a488ee7d

Disable 44056 test with debug on macos.

view details

Aman Arora

commit sha 1acccb0f52bc5812ae9431b36b6f8f232a513d1f

Make hir ProjectionKind more precise This commit also categorizing access as Field, Index, or Subslice. Ideas are taken from `mir::ProjectionElem`. Proposed changes: https://github.com/rust-lang/project-rfc-2229/blob/master/hir-place-target.md Closes: https://github.com/rust-lang/project-rfc-2229/issues/1, https://github.com/rust-lang/project-rfc-2229/issues/2 Co-authored-by: Aman Arora <me@aman-arora.com> Co-authored-by: Chris Pardy <chrispardy36@gmail.com> Co-authored-by: Dhruv Jauhar <dhruvjhr@gmail.com>

view details

Eric Huss

commit sha 9f91a9540d5058eb7b384d1a58e81a4672fea7b4

Ignore changes when debug assertions are enabled.

view details

Mohsen Zohrevandi

commit sha 1466598e19321bc6b97aef8271a317e78211d54d

Address review comments

view details

Stein Somers

commit sha 2aa3133c530b40ea0448d3c6a5507aeb40aaa558

Add and fix BTreeMap comments

view details

Guillaume Gomez

commit sha 382d5bb715859423a086c6b26e651c18adf0dcb9

Focus on the current file in the source file sidebar

view details

Andy Russell

commit sha c3ee75d956a52791dd0e50391f941030a112f7ef

rustdoc: glue tokens before highlighting Fixes #72684. This commit also modifies the signature of `Classifier::new` to avoid copying the source being highlighted.

view details

push time in 2 months

push eventLezzz/rust

Valentin Lazureanu

commit sha dced0b8900a653a59643bb06fdf812c5f8c7a9a9

Rename TypeckTables to TypeckResults.

view details

push time in 2 months

push eventLezzz/rust

Valentin Lazureanu

commit sha 73a8e8e5ff3a4de8a5ab8372188f099d1efdfe1b

Rename TypeckTables to TypeckResults.

view details

push time in 2 months

push eventLezzz/rust

Yoshua Wuyts

commit sha a31f103fd27bde3f83b9dd54af8e41d64e5001f4

Add core::future::{poll_fn, PollFn}

view details

Chris Denton

commit sha 912963bd0856239828253af8d04e4f62e75cafd7

Remove legacy InnoSetup GUI installer On Windows the InnoSetup installer was superseded by the MSI installer. It's no longer needed.

view details

djugei

commit sha b4337ab8c387658b7012fa242e429f46c5f31141

added .collect() into String from Box<str> with fake feature/stability annotation

view details

Tomasz Miąsko

commit sha 291dce91b24d70382ebf1116fa836fd91960de84

Fallback to xml.etree.ElementTree The xml.etree.cElementTree has been deprecated since Python 3.3 and removed in Python 3.9 https://bugs.python.org/issue36543.

view details

Alexis Bourget

commit sha 049f6eaa792fbbf2b727fc278ddd23d1e11d57bd

Fixing broken link for the Eq trait

view details

Caleb Zulawski

commit sha 144206e6d8c1ab4ffdbaf6d7b0f5a4201c0f2da4

Don't implement Fn* traits for #[target_feature] functions

view details

Teddy_Wang

commit sha 40ee620e51c86c72e3c2b65df71f5f0a4a79797f

Added a lint for .map(|x| x)

view details

Caleb Zulawski

commit sha c98b4c8fdde7812d7af5a060a1e22fd7e3775d3f

Add error note when trying fn as Fn trait

view details

pankajchaudhary5

commit sha 46bfc48272ba5312c439557e2901e1a4778e9487

Added proper explanation of ErrorCode-E0687

view details

mark

commit sha 3f6928f1f6eff367e6ddbfb63ebc5e568ffe0eb1

move contributing.md to rustc-dev-guide and point at getting started

view details

Matthias Krüger

commit sha 1d0378c454de72ddcfc08bcc105744923ef2d4d4

impl From<char> for String This allows us to write fn char_to_string() -> String { 'a'.into() } which was not possible before.

view details

Tomasz Miąsko

commit sha 5c20ef433b48fce78c07208710bcc8b53965eeb1

bootstrap: Configurable musl libdir Make it possible to customize the location of musl libdir using musl-libdir in config.toml, e.g., to use lib64 instead of lib.

view details

Matthias Krüger

commit sha 2cde4932c7e8bd6000378af41029299ccf6eea69

add test for char into string

view details

CAD97

commit sha 7779a11448927e208ed6eb9bb609dd23595f77ce

Use step_unchecked more liberally

view details

Alexis Bourget

commit sha 6e8251742071d56545b6ce160ed71bb60597ee01

Documenting the separate behaviors of edition 2015 and 2018

view details

Alexis Bourget

commit sha 59701360dc0c76bfa45204d307ac5055f8bff538

Fix some small mistakes

view details

Anirban

commit sha 886f81e1d0883f67fbc81b8ece61b1c33f6923d2

Fix sentence structure Fixed grammar and sentence structure on appropriate instances.

view details

flip1995

commit sha 80bcbf521c7ff95e38a7567432b5519cc18e5b2a

Merge commit 'c2c07fa9d095931eb5684a42942a7b573a0c5238' into clippyup

view details

Teddy_Wang

commit sha fb4f9a0ad7a4656beb01c85b02b3e6ef15d914ec

Fix pattern match of ExprKind::MethodCall

view details

bors

commit sha 583d64493484f72425ecac55eaf5eddbba10b132

Auto merge of #5694 - wangtheo:issue-5626, r=matthiaskrgr #5626: lint iterator.map(|x| x) changelog: adds a new lint for iterator.map(|x| x) (see https://github.com/rust-lang/rust-clippy/issues/5626) The code also lints for result.map(|x| x) and option.map(|x| x). Also, I'm not sure if I'm checking for type adjustments correctly and I can't think of an example where .map(|x| x) would apply type adjustments.

view details

push time in 2 months

push eventLezzz/rust

Valentin Lazureanu

commit sha 0f990c46e81ec00f9197bf1117460ae6d5b45622

Rename TypeckTables to TypeckResults.

view details

push time in 3 months

push eventLezzz/rust

Valentin Lazureanu

commit sha e3cbb626250b815fb0cdd3c0c2f16db96ec0c4dd

Rename TypeckTables to TypeckResults.

view details

push time in 3 months

push eventLezzz/rust

Valentin Lazureanu

commit sha ec9b5d9f0485523774af6077ecb28b45682d019b

Rename TypeckTables to TypeckResults.

view details

push time in 3 months

push eventLezzz/rust

Dylan DPC

commit sha fda594e6ae5c430475120944b8a0e92fe8f206a5

Rollup merge of #72890 - davidtwco:issue-66202-normalize-and-transparent-improper-ctypes, r=varkor improper ctypes: normalize return types and transparent structs Fixes #66202. See each commit individually (except the first which adds a test) for more detailed explanations on the changes made. In summary, this PR ensures that return types are normalized before being checked for FFI-safety, and that transparent newtype wrappers are FFI-safe if the type being wrapped is FFI-safe (often true previously, but not if, after substitution, all types in a transparent newtype were zero sized).

view details

Dylan DPC

commit sha 8addb2e684dfbe0cd2e16a769485a093f9b2de32

Rollup merge of #72897 - lcnr:structurally-match-normalize, r=pnkfelix normalize adt fields during structural match checking fixes #72896 currently only fixes the issue itself and compiles stage 1 libs. I believe we have to use something else to normalize the adt fields here, as I expect some partially resolved adts to cause problems :thinking: stage 1 libs and the test itself pass, not sure about the rest... Will spend some more time looking into it tomorrow. r? @pnkfelix cc @eddyb

view details

Dylan DPC

commit sha 024f025934a40056364be4a4da4f7e078b419f68

Rollup merge of #73005 - Aaron1011:fix/error-overflow, r=estebank Don't create impl candidates when obligation contains errors Fixes #72839 In PR #72621, trait selection was modified to no longer bail out early when an error type was encountered. This allowed us treat `ty::Error` as `Sized`, causing us to avoid emitting a spurious "not sized" error after a type error had already occured. However, this means that we may now try to match an impl candidate against the error type. Since the error type will unify with almost anything, this can cause us to infinitely recurse (eventually triggering an overflow) when trying to verify certain `where` clauses. This commit causes us to skip generating any impl candidates when an error type is involved.

view details

Dylan DPC

commit sha e1cd8c41a559276a2a8ff62085ded220cccb88f3

Rollup merge of #73023 - ayushmishra2005:remove_noisy_suggestion, r=davidtwco Remove noisy suggestion of hash_map Remove noisy suggestion of hash_map #72642 fixes #72642

view details

Dylan DPC

commit sha 0a77c8c2956259eb6811b51fac095c8ed21e6760

Rollup merge of #73070 - ayazhafiz:i/72819, r=nikomatsakis Add regression test for const generic ICE in #72819 Closes #72819

view details

Dylan DPC

commit sha e04e3c89cc08546c5c762ea915cb72d4069a733e

Rollup merge of #73157 - Aaron1011:where-oh-where-has-my-little-span-gone, r=ecstatic-morse Don't lose empty `where` clause when pretty-printing Previously, we would parse `struct Foo where;` and `struct Foo;` identically, leading to an 'empty' `where` clause being omitted during pretty printing. This will cause us to lose spans when proc-macros involved, since we will have a collected `where` token that does not appear in the pretty-printed item. We now explicitly track the presence of a `where` token during parsing, so that we can distinguish between `struct Foo where;` and `struct Foo;` during pretty-printing

view details

Dylan DPC

commit sha 2b8f1eccaa138a2a4af61356231c33d7d93ed993

Rollup merge of #73184 - mati865:fix-mingw-libs-order, r=petrochenkov Reoder order in which MinGW libs are linked to fix recent breakage Recent upstream mingw-w64 changes made libmsvcrt depend on libmingwex breaking compilation in some cases when using **external** MinGW. Applying this change to the master fixes nightly and stage{1,2} build. For stage0 one has to export `RUSTFLAGS_BOOTSTRAP='-C link-arg=-lmsvcrt'` until this PR lands in bootstrap compiler. Therefore I'm humbly asking to also backport it to the beta and update bootstrap compiler.

view details

Guillaume Gomez

commit sha dc230c06b226947a5a9980d2947118fd4a8ece9e

Clean up E0648 explanation

view details

Guillaume Gomez

commit sha 50a42fe5134fd8dbd5bc6df110654a31ee059a62

Create new error code E0762 for unterminated char literals

view details

Guillaume Gomez

commit sha 7bd87cfac2ca4c2c19b04018774b1fb1a9b39e48

Add tests for E0762

view details

Mihail Malo

commit sha 5859f6e4f792afb663ac2dc98191cca08ac9b4ae

Fix doctest template `saturating_add` example was not parameterized, but passed because the `u8` would saturate successfully

view details

Eric Huss

commit sha cd02052ad083ae0927a08483035b5dca214bdd0d

Fix emcc failure for wasm32.

view details

Manish Goregaokar

commit sha 34c6b38e68f2e88bcc6c943494a7c05d35a71f17

Add tests for macro@ and derive@

view details

Ralf Jung

commit sha f507748ce49f8e9ce5dc76bb7811a374c814923f

x.py: with --json-output, forward cargo's JSON

view details

bors

commit sha 449e8eaa286e407c9cd8cac655b77998fd53db6b

Auto merge of #73213 - ehuss:fix-emsdk, r=Mark-Simulacrum Fix emcc failure for wasm32. The wasm32 job is currently failing on CI with the error `ERROR: llc executable not found at /usr/bin/llc`. The issue is that https://github.com/emscripten-core/emsdk/pull/472 has changed how emsdk discovers its configuration. We were relying on the global behavior that would use a configuration from the home directory. However, it looks like emsdk is moving away from that approach. This change adds the necessary env var for emcc to find the correct configuration. There are a few alternate approaches this could take. The `--no-embedded` option could be passed to `emsdk activate` to use the old behavior, but it seems like they want to move away from that. Another option is to source `emsdk_env.sh`, which is how these env vars normally get set. I'm not entirely sure how to do that easily in a Dockerfile, though.

view details

Rich Kadel

commit sha d139a720a2c0ad7066c43edad6ec6c2aa9613740

Merge pull request #2 from rust-lang/master update from origin 2020-06-10

view details

Esteban Küber

commit sha c29b3fa1484c625bd34cb4d94fc76f36c6233447

On recursive ADT, provide indirection structured suggestion

view details

Esteban Küber

commit sha 7cde07e5cc5cfc1665dd64e4c06482c2f10b693a

review comments: only suggest one substitution

view details

Amanieu d'Antras

commit sha 2af53e9a15aed1e9798867c9233a722530d03177

Add -O compile flag to test

view details

Aaron Hill

commit sha 28946b3486d507418b8a4acb92d5e2baae193d65

Track span of function in method calls, and use this in #[track_caller] Fixes #69977 When we parse a chain of method calls like `foo.a().b().c()`, each `MethodCallExpr` gets assigned a span that starts at the beginning of the call chain (`foo`). While this is useful for diagnostics, it means that `Location::caller` will return the same location for every call in a call chain. This PR makes us separately record the span of the function name and arguments for a method call (e.g. `b()` in `foo.a().b().c()`). This `Span` is passed through HIR lowering and MIR building to `TerminatorKind::Call`, where it is used in preference to `Terminator.source_info.span` when determining `Location::caller`. This new span is also useful for diagnostics where we want to emphasize a particular method call - for an example, see https://github.com/rust-lang/rust/pull/72389#discussion_r436035990

view details

push time in 3 months

more