Relative to Rustc

gccrs error code support 🦀

There are some errors which are not longer emitted by rustc-1.49.0.

Error codeIs Emitted by rustc-1.49.0Is Error generated by gccrsError support in gccrsDescription
E0001NoYesIssueUnreachable Pattern in Match Statement
E0002NoNo-Empty Match Expression on Non-Empty Type
E0004YesNoIssueNon-Exhaustive Patterns: Matching Error
E0005YesYesIssuePatterns used to bind names must be irrefutable, that is, they must guarantee that a name will be extracted in all cases.
E0007NoYesNocannot bind by-move with sub-bindings
E0010YesYesNoallocations are not allowed in constants
E0015YesYesYesA non-const function was called in a const context.
E0023YesYesYesIncorrect Number of Fields in Pattern Extraction
E0026YesYesYesNon-Existent Field Extraction in Struct Pattern also need to refactor this
E0027YesYesYesA pattern for a struct fails to specify a sub-pattern for every one of the struct’s fields.
E0029YesYesNoNon-Comparable Range Error (Something other than numbers and characters has been used for a range)
E0030YesNo-Empty Range Pattern Error
E0033YesYesNoA trait type has been dereferenced (Internal Compile error in gccrs)
E0034YesYesYes Issue Issue-FixAmbiguous Method Call Error - more than one method has the same prototype
E0038YesYesNo - IssueTraits that are declared as Trait: Sized or which otherwise inherit a constraint of Self:Sized are not object-safe.
E0040YesYesNoExplicit use of destructor method
E0044YesNoIssueType or Const Parameters Not Allowed on Foreign Items
E0045YesNoYes - IssueVariadic Parameters Used on Non-C ABI Function
E0046YesYesYesMissing Items in Trait Implementation - Issue
E0049YesYesNoAn attempted implementation of a trait method has the wrong number of type or const parameters - Error Link
E0050YesYesNoAn attempted implementation of a trait method has the wrong number of function parameters - godbolt-link](https://godbolt.org/z/8Waa3KK19) - [gccrs error - rustc fine`
E0053YesYesYesThe parameters of any trait method must match between a trait implementation and the trait definition - method ‘x’ has an incompatible type for trait ‘y’
E0054YesYesYesInvalid Cast of Integer to Bool
E0055YesYesNo - need reviewRecursion Limit Exceeded
E0057YesYesIssueAn invalid number of arguments was given when calling a closure - compiler-explorer
E0059YesYesNoIncorrect Usage of Angle-Bracket Notation in Function Traits - (Failed to resolve type path error)
E0060YesYesNoVariadic Function Requires Minimum Number of Arguments - (likewise same as failed to resolve type path in this scope)
E0061YesYesYesInvalid number of arguments was passed when calling a function - unexpected number of arguments x expected y
E0062YesYesIssueA struct’s or struct-like enum variant’s field was specified more than once.
E0063YesYesYes - Missing-Location-info-ISSUE - no-fields-in-constructorMissing Field in Struct or Struct-like Enum Variant - constructor is missing fields
E0069YesYesNo - Work on this laterMismatch between function return type & the value being returned
E0070YesYesYes - IssueAn assignment operator was used on a non-place expression.
E0071YesYesNo - Work on this laterA structure-literal syntax was used to create an item that is not a structure or enum variant.
E0072YesYesNo - Work on this laterA recursive type has infinite size because it doesn’t have an indirection.
E0073YesYesNo - Work on this laterYou cannot define a struct (or enum) Foo that requires an instance of Foo in order to make a new Foo value.
E0074YesYesNo - Work on this later -smid featureWhen using the #[simd] attribute on a tuple struct, the components of the tuple struct must all be of a concrete, nongeneric type so the compiler can reason about how to use SIMD with them.
E0075YesYesNo - Work on this later - simd macro errorA #[simd] attribute was applied to an empty tuple struct.
E0076YesYesNo - Work on this later - simd macro errorAll types in a tuple struct aren’t the same when using the #[simd] attribute.
E0077YesYesNo - Work on this later - simd macro errorA tuple struct’s element isn’t a machine type when using the #[simd] attribute.
E0080YesYesNo -Issue-linkA constant value failed to get evaluated.
E0081YesYesNoA discriminant value is present more than once.
E0093YesYesYesAn unknown intrinsic function was declared.
E0107YesYesYesAn incorrect number of generic arguments was provided.
E0116YesYesNO - Internal compile ErrorAn inherent implementation was defined for a type outside the current crate.
E0124YesYesYesA struct was declared with two fields having the same name.
E0133YesYesYesUnsafe code was used outside of an unsafe function or block.
E0164YesYesNo - IssueSomething which is neither a tuple struct nor a tuple variant was used as a pattern.
E0184YesYesICE - Issuethe trait Copy may not be implemented for this type; the type has a destructor
E0229YesYesYesAssociated Type Binding Outside of Type Parameter Declaration and Where Clause
E0267YesYesIssueA loop keyword (break or continue) was used inside a closure but outside of any loop.
E0268YesYesYesA loop keyword (break or continue) was used outside of a loop.
E0271YesYesYesA type mismatched an associated type of a trait.
E0277YesYesYesType Does Not Implement Expected Trait - the type [{integer}] cannot be indexed by u32
E0282YesYesYesThe compiler could not infer a type and asked for a type annotation.
E0303NoYesNo - Added as subtask on #2509pattern bindings are not allowed after an @
E0308YesYesYes array-caseExpected type did not match the received type.
E0323YesYesYesAn associated const was implemented when another trait item was expected.
E0324YesYesIssue - NoA method was implemented when another trait item was expected.
E0380YesYesYesAn auto trait was declared with a method or an associated item.
E0390YesNoIssue No (Raise issue- https://godbolt.org/z/Pr3ae4ovP)A method or constant was implemented on a primitive type.
E0391YesYesYesA type dependency cycle has been encountered.
E0404YesYesICE - IssueA type that is not a trait was used in a trait position, such as a bound or impl.
E0412YesYesYesA used type name is not in scope.
E0423YesYesYes - IssueAn identifier was used like a function name or a value was expected and the identifier exists but it belongs to a different namespace.
E0425YesYesYesUse of unresolved name
E0426YesYesYesAn undeclared label was used.
E0431YesYesIssue - NoAn invalid self import was made.
E0433YesYesYesFailed to resolve. Use of Undeclared Crate, Module, or Type
E0532YesYesYesArm Does Not Match Expected Kind - expected tuple struct or tuple variant, found struct variant
E0534YesYesYesThe inline attribute was malformed.
E0535YesYesYesAn unknown argument was given to the inline attribute.
E0541YesYesYesAn unknown meta item was used.
E0554YesYesNoFeature attributes are only allowed on the nightly release channel.
E0571YesYesYesA break statement with an argument appeared in a non-loop loop.
E0572YesYesYES Issue (ICE)A return statement was found outside of a function body.
E0573YesYesIssue YesSomething other than a type has been used when one was expected.
E0592YesYesYesThis error occurs when you defined methods or associated functions with same name.
E0599YesYesYesThis error occurs when a method is used on a type which doesn’t implement it:
E0601YesYesICE - IssueNo main function was found in a binary crate.
E0604YesYesYesA cast to char was attempted on a type other than u8
E0605YesYesNeed Rust standad library YesAn invalid cast was attempted.
E0606YesYesYesAn incompatible cast was attempted.
E0607YesYesNo Need rust slA cast between a thin and a fat pointer was attempted.
E0618YesYesNoAttempted to call something which isn’t a function nor a method.
E0620YesYesYesA cast to an unsized type was attempted.
E0623YesYesNo - Need rust slA lifetime didn’t match what was expected.
E0635YesYesYesThe #![feature] attribute specified an unknown feature.
E0641YesYesNo - Need rust slAttempted to cast to/from a pointer with an unknown kind.
E0658YesYesYes mut-ref Top level patterns in le experssionAn unstable feature was used
E0703YesYesYesInvalid ABI (Application Binary Interface) used in the code.
E0720YesYesICE - IssueAn impl Trait type expands to a recursive type.
E0753YesYesYesAn inner doc comment was used in an invalid context.
E0769YesYesYesA tuple struct or tuple variant was used in a pattern as if it were a struct or struct variant.
E0781YesYesNo - Need rust slThe C-cmse-nonsecure-call ABI can only be used with function pointers.

Top