Code compiles on playground but fails when passed via stdin to rustc

github.com/rust-lang/rust

When compiling without a specified --edition, emit a note (#158102)

mainestebank:note-default-edition

opened 08:28PM - 18 Jun 26 UTC

        estebank
      

+178
-43

Would someone have the energy to write the MCP for merging this change? I believe that we might have to coordinate with cargo (to ensure the edition is being passed in…

Why is strict_div implemented in terms of overflowing_div for signed integers?

Your question doesn't seem to be answered here:

github.com/rust-lang/rust

Implement strict integer operations that panic on overflow (#116090)

masterrmehri01:strict_integer_ops

opened 04:50AM - 23 Sep 23 UTC

        rmehri01
      

+996
-15

This PR implements the first part of the ACP for adding panic on overflow style …arithmetic operations…

Read more →
Crowdsourcing request: What syntax changes that will affect the AST are currently in flight?

looking through recent commits to rustc_parse:

github.com/rust-lang/rust

Parse mut restrictions

committed 08:33AM - 24 May 26 UTC

      CoCo-Japan-pan
    

+124
-47

github.com/rust-lang/rust

add move(expr) syntax

committed 01:22PM - 07 May 26 UTC

      TaKO8Ki
    

+77
-4

github.com/rust-lang/rust

Parse view type syntax, mark it as…

Read more →
Wasm32: Rust should not spill v128 function params into shadow stack

You are allowed to pass core::arch::wasm32::v128 around even when the v128 target feature is disabled. In that case we have to pass v128 values by-ref. To prevent ABI mismatches when one crate disables v128 (libcore has it disabled) while other crates have it enabled, we have to unconditionally pass v128 by-ref.

github.com/rust-lang/rust

####…

Read more →
core::path::Path

Related: there's an issue about also making it possible to deal with Windows paths (in a lexical way) on Unix and vice versa.

github.com/rust-lang/rust

Support Windows path manipulation on other platforms

opened 03:51AM - 15 May 19 UTC

      mathstuf
    

T-libs-api C-feature-request A-io

It'd be nice if the facilities under std::os which don't use platform-specific……

Read more →
[Pre-pre RFC] Allow exclusion of trait methods for (certain) unsatisfiable where bounds

Related:

  • Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
  • Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Read more →
[Pre-pre RFC] Allow exclusion of trait methods for (certain) unsatisfiable where bounds

Related:

  • Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
  • Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Read more →
[Pre-pre RFC] Allow exclusion of trait methods for (certain) unsatisfiable where bounds

Related:

  • Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
  • Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Read more →
[Pre-pre RFC] Allow exclusion of trait methods for (certain) unsatisfiable where bounds

Related:

  • Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
  • Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Read more →
[Pre-pre RFC] Allow exclusion of trait methods for (certain) unsatisfiable where bounds

Related:

  • Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
  • Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Read more →
[Pre-pre RFC] Allow exclusion of trait methods for (certain) unsatisfiable where bounds

Related:

  • Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
  • Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Read more →
[Pre-pre RFC] Allow exclusion of trait methods for (certain) unsatisfiable where bounds

Related:

  • Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
  • Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Read more →
[Pre-pre RFC] Allow exclusion of trait methods for (certain) unsatisfiable where bounds

Related:

  • Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
  • Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Read more →
[Pre-pre RFC] Allow exclusion of trait methods for (certain) unsatisfiable where bounds

Related:

  • Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
  • Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Read more →
[Pre-pre RFC] Allow exclusion of trait methods for (certain) unsatisfiable where bounds

Related:

  • Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
  • Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Read more →
[Pre-Pre RFC] Ability to specify a trait as marker trait

RFC'd and accepted over a decade ago.

github.com/rust-lang/rust

Tracking issue for allowing overlapping implementations for marker trait

opened 05:09PM - 16 Nov 15 UTC

      nikomatsakis
    

A-trait-system T-lang B-unstable B-RFC-implemented C-tracking-issue F-marker_trait_attr S-tracking-needs-to-bake T-types S-tracking-blocked

Tracking issue for…

Read more →
[Pre-Pre RFC] Ability to specify a trait as marker trait

RFC'd and accepted over a decade ago.

github.com/rust-lang/rust

Tracking issue for allowing overlapping implementations for marker trait

opened 05:09PM - 16 Nov 15 UTC

      nikomatsakis
    

A-trait-system T-lang B-unstable B-RFC-implemented C-tracking-issue F-marker_trait_attr S-tracking-needs-to-bake T-types S-tracking-blocked

Tracking issue for…

Read more →
[Pre-Pre RFC] Ability to specify a trait as marker trait

RFC'd and accepted over a decade ago.

github.com/rust-lang/rust

Tracking issue for allowing overlapping implementations for marker trait

opened 05:09PM - 16 Nov 15 UTC

      nikomatsakis
    

A-trait-system T-lang B-unstable B-RFC-implemented C-tracking-issue F-marker_trait_attr S-tracking-needs-to-bake T-types S-tracking-blocked

Tracking issue for…

Read more →
[Pre-Pre RFC] Ability to specify a trait as marker trait

RFC'd and accepted over a decade ago.

github.com/rust-lang/rust

Tracking issue for allowing overlapping implementations for marker trait

opened 05:09PM - 16 Nov 15 UTC

      nikomatsakis
    

A-trait-system T-lang B-unstable B-RFC-implemented C-tracking-issue F-marker_trait_attr S-tracking-needs-to-bake T-types S-tracking-blocked

Tracking issue for…

Read more →
[Pre-Pre RFC] Ability to specify a trait as marker trait

RFC'd and accepted over a decade ago.

github.com/rust-lang/rust

Tracking issue for allowing overlapping implementations for marker trait

opened 05:09PM - 16 Nov 15 UTC

      nikomatsakis
    

A-trait-system T-lang B-unstable B-RFC-implemented C-tracking-issue F-marker_trait_attr S-tracking-needs-to-bake T-types S-tracking-blocked

Tracking issue for…

Read more →
Idea: trait methods with un-overridable implementations

github.com/rust-lang/rust

final methods should work the same as without it (if it works without it)

opened 09:31AM - 10 Mar 26 UTC

mu001999

I-unsound C-bug T-types A-dyn-trait F-final_associated_functions

Tracking: https://github.com/rust-lang/rust/issues/131179 Found when trying to …use final to impl Error::type_id in https://github.com/rust-lang/rust/pull/153598, this…

Read more →
Idea: trait methods with un-overridable implementations

github.com/rust-lang/rust

final methods should work the same as without it (if it works without it)

opened 09:31AM - 10 Mar 26 UTC

mu001999

I-unsound C-bug T-types A-dyn-trait F-final_associated_functions

Tracking: https://github.com/rust-lang/rust/issues/131179 Found when trying to …use final to impl Error::type_id in https://github.com/rust-lang/rust/pull/153598, this…

Read more →
Idea: trait methods with un-overridable implementations

github.com/rust-lang/rust

final methods should work the same as without it (if it works without it)

opened 09:31AM - 10 Mar 26 UTC

mu001999

I-unsound C-bug T-types A-dyn-trait F-final_associated_functions

Tracking: https://github.com/rust-lang/rust/issues/131179 Found when trying to …use final to impl Error::type_id in https://github.com/rust-lang/rust/pull/153598, this…

Read more →
Idea: trait methods with un-overridable implementations

github.com/rust-lang/rust

final methods should work the same as without it (if it works without it)

opened 09:31AM - 10 Mar 26 UTC

mu001999

I-unsound C-bug T-types A-dyn-trait F-final_associated_functions

Tracking: https://github.com/rust-lang/rust/issues/131179 Found when trying to …use final to impl Error::type_id in https://github.com/rust-lang/rust/pull/153598, this…

Read more →
Custom Cargo Command to Show Only Errors (Avoid Setting RustFLAGS Every Time)

Well then, one followup error that recently annoyed me came to mind, so I tried writing a fix for it:

github.com/rust-lang/rust

Don’t report missing fields in struct exprs with syntax errors. (#153227)

mainkpreid:struct-missing-field

opened 05:18PM - 28 Feb 26 UTC

kpreid

+232 -95

@Noratrieb told mehow-only-errors-avoid-setting-rustflags-every-time/24032/7?u=kpreid) that…

Read more →
Custom Cargo Command to Show Only Errors (Avoid Setting RustFLAGS Every Time)

Well then, one followup error that recently annoyed me came to mind, so I tried writing a fix for it:

github.com/rust-lang/rust

Don’t report missing fields in struct exprs with syntax errors. (#153227)

mainkpreid:struct-missing-field

opened 05:18PM - 28 Feb 26 UTC

kpreid

+232 -95

@Noratrieb told mehow-only-errors-avoid-setting-rustflags-every-time/24032/7?u=kpreid) that…

Read more →
Custom Cargo Command to Show Only Errors (Avoid Setting RustFLAGS Every Time)

Well then, one followup error that recently annoyed me came to mind, so I tried writing a fix for it:

github.com/rust-lang/rust

Don’t report missing fields in struct exprs with syntax errors. (#153227)

mainkpreid:struct-missing-field

opened 05:18PM - 28 Feb 26 UTC

kpreid

+232 -95

@Noratrieb told mehow-only-errors-avoid-setting-rustflags-every-time/24032/7?u=kpreid) that…

Read more →
Custom Cargo Command to Show Only Errors (Avoid Setting RustFLAGS Every Time)

Well then, one followup error that recently annoyed me came to mind, so I tried writing a fix for it:

github.com/rust-lang/rust

Don’t report missing fields in struct exprs with syntax errors. (#153227)

mainkpreid:struct-missing-field

opened 05:18PM - 28 Feb 26 UTC

kpreid

+232 -95

@Noratrieb told mehow-only-errors-avoid-setting-rustflags-every-time/24032/7?u=kpreid) that…

Read more →
Custom Cargo Command to Show Only Errors (Avoid Setting RustFLAGS Every Time)

Well then, one followup error that recently annoyed me came to mind, so I tried writing a fix for it:

github.com/rust-lang/rust

Don’t report missing fields in struct exprs with syntax errors. (#153227)

mainkpreid:struct-missing-field

opened 05:18PM - 28 Feb 26 UTC

kpreid

+232 -95

@Noratrieb told mehow-only-errors-avoid-setting-rustflags-every-time/24032/7?u=kpreid) that…

Read more →
Custom Cargo Command to Show Only Errors (Avoid Setting RustFLAGS Every Time)

Well then, one followup error that recently annoyed me came to mind, so I tried writing a fix for it:

github.com/rust-lang/rust

Don’t report missing fields in struct exprs with syntax errors. (#153227)

mainkpreid:struct-missing-field

opened 05:18PM - 28 Feb 26 UTC

kpreid

+232 -95

@Noratrieb told mehow-only-errors-avoid-setting-rustflags-every-time/24032/7?u=kpreid) that…

Read more →
Page 1 Older →