Files
carbon-lang/explorer/testdata/alias/struct_alias.carbon
T
Jon Ross-Perkins 129f31710d Disable autoupdate in explorer tests. (#4023)
Just replacing AUTOUPDATE with NOAUTOUPDATE, and removing the autoupdate
script. Tests will still run, but autoupdate may need to be fixed if
significant changes are made.

I noticed this while trying to autoupdate for #4007 (because we verify
that tests have been autoupdated). Autoupdate was likely broken by
#3449.

Trying to run with no changes gives:

```
CHECK failure at testing/file_test/file_test_base.cpp:801: !absl::GetFlag(FLAGS_test_targets_file).empty(): Missing --test_targets_file.
```

This is because the `file_test` rule creates a file with test inputs
that it runs with, which the prebuilt binary doesn't provide.

A local kludge to create a `file_test` target not using prebuilt_binary
showed another error:

```
: CommandLine Error: Option ': CommandLine Error: Option 'parser_debug' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options
trace_phase' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options
```

I'm thinking here that the explorer code hasn't been in enough use, and
we're seeing some rot as a consequence. Rather than trying to maintain
it, I'm suggesting to go with NOAUTOUPDATE.
2024-06-04 16:44:36 +00:00

27 lines
627 B
Plaintext

// Part of the Carbon Language project, under the Apache License v2.0 with LLVM
// Exceptions. See /LICENSE for license information.
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
//
// NOAUTOUPDATE
package ExplorerTest api;
alias AB = {.a: i32, .b: i32};
alias BA = {.b: i32, .a: i32};
fn Main() -> i32 {
var ab: AB = {.b = 1, .a = 2};
var ba: BA = ab;
Print("ab.a: {0}", ab.a);
Print("ab.b: {0}", ab.b);
Print("ba.a: {0}", ba.a);
Print("ba.b: {0}", ba.b);
return 0;
}
// CHECK:STDOUT: ab.a: 2
// CHECK:STDOUT: ab.b: 1
// CHECK:STDOUT: ba.a: 2
// CHECK:STDOUT: ba.b: 1
// CHECK:STDOUT: result: 0