Skip to content

Error spans for illegal extern "ABI" #14499

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
liigo opened this issue May 29, 2014 · 1 comment
Closed

Error spans for illegal extern "ABI" #14499

liigo opened this issue May 29, 2014 · 1 comment

Comments

@liigo
Copy link
Contributor

liigo commented May 29, 2014

pub extern "xxxxx" fn add(x: int, y: int) -> int {
    x + y
}
hello.rs:9:20: 9:22 error: illegal ABI: expected one of [cdecl, stdcall, fastcall, aapcs, win64, Rust, C, system, rust-intrinsic], found `xxxxx`
hello.rs:9 pub extern "xxxxx" fn add(x: int, y: int) -> int {
                              ^~
error: aborting due to previous error
@luqmana
Copy link
Member

luqmana commented May 29, 2014

Dupe of #8537.

@luqmana luqmana closed this as completed May 29, 2014
bors added a commit that referenced this issue May 30, 2014
Fixes #8537
Fixes #14499 (duplicate of #8537)

Old:
```rust
test.rs:2 	pub extern "xxxxx" fn add(x: int, y: int) -> int {
          	                   ^~
```

New:
```rust
test.rs:2 	pub extern "xxxxx" fn add(x: int, y: int) -> int {
          	           ^~~~~~~
```
bors added a commit to rust-lang-ci/rust that referenced this issue Jun 5, 2023
minor: Fix some simple FIXMEs

Each FIXME fix has been split into its own commit, since they're all pretty independent changes.

(Forgot to open a PR for this a few days ago, oops)
flip1995 pushed a commit to flip1995/rust that referenced this issue Apr 3, 2025
…-lang#14499)

This is a style-only change in order to use match ergonomics by removing
unneeded `&` and `ref`.

changelog: none
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants