-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Getting started instructions not working #4734
Comments
yes the Core.Print function has moved into the "io" library in Core. You can have a look at the |
The missing nightly is because the actions started failing, not because of the holidays per se: https://github.com/carbon-language/carbon-lang/actions/runs/12450480722/job/34757345786 |
danakj
added a commit
to danakj/carbon-lang
that referenced
this issue
Dec 23, 2024
The Core.Print function has moved into the "io" library, so it needs to be imported into scope. Part of issue carbon-language#4734
danakj
added a commit
to danakj/carbon-lang
that referenced
this issue
Dec 23, 2024
The path moved from ./bazel-bin/toolchain/install/run_carbon to ./bazel-bin/toolchain/carbon in 13502b7. Closes carbon-language#4734
danakj
added a commit
to danakj/carbon-lang
that referenced
this issue
Dec 23, 2024
The path moved from ./bazel-bin/toolchain/install/run_carbon to ./bazel-bin/toolchain/carbon in 13502b7. Part of issue carbon-language#4734
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug:
First issue is that I guess due to holidays there were no recent releases so
VERSION="$(date -d yesterday +0.0.0-0.nightly.%Y.%m.%d)"
does not work.
Second issue is that when I manually change date running the steps fails with:
forty_two.carbon:1:12: error: member name
Printnot found in
Corefn Run() { Core.Print(42); }
I presume language changed since documentation was written.
Link to documentation:
https://github.com/carbon-language/carbon-lang?tab=readme-ov-file#getting-started
What should it say instead?
would be nice if there was easy way to point to last release.
would be nice if program we are echoing compiles.
Any other information, logs, or outputs that you want to share?
I reduced the script so maybe bug is on my side, although I doubt it. This is my exact script:
The text was updated successfully, but these errors were encountered: