Skip to content

Move explorer out of toolchain git repo #5270

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

Merged
merged 7 commits into from
Apr 9, 2025

Conversation

danakj
Copy link
Contributor

@danakj danakj commented Apr 8, 2025

The explorer is an archived codebase, without a plan to restart development on it. The costs incurred by keeping it in the main git repo can be alleviated by moving it to a new sibling repo, without diminishing the usefulness of the explorer codebase for demonstrating implementation of the carbon language design.

@danakj danakj added proposal A proposal proposal draft Proposal in draft, not ready for review labels Apr 8, 2025
@danakj danakj force-pushed the proposal-explorer branch 6 times, most recently from 5e6e220 to 7280907 Compare April 8, 2025 17:16
@danakj danakj force-pushed the proposal-explorer branch from 7280907 to 058e733 Compare April 8, 2025 17:18
@danakj danakj marked this pull request as ready for review April 8, 2025 17:19
@github-actions github-actions bot added proposal rfc Proposal with request-for-comment sent out and removed proposal draft Proposal in draft, not ready for review labels Apr 8, 2025
@github-actions github-actions bot requested a review from chandlerc April 8, 2025 17:19
Copy link
Contributor

@jonmeow jonmeow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SG, even though I'm uncertain about the value of an archive repo, I think this is an improvement over the status quo.

repository.
4. Add a `README.md` to the `explorer` repository that explains explorer is
archived and not under active development.
5. Delete `//explorer` in the main `carbon-lang` repository.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is Compiler Explorer still building explorer (visible at https://carbon.compiler-explorer.com/z/b61T6n44h)? Maybe something to double-check if you're not sure -- even with the archive repo, might want to just ensure it's turned off.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am unsure if it's building it still. There's nothing visible in the compiler-explorer git repo that would suggest either way. But since the binary isn't part of the nightly release tarball, and we don't provide a binary of the explorer in some other way, I am guessing that it is still being built.

If this is approved I will kick off a PR with compiler-explorer to remove the carbon-explorer, and that can prompt them to also stop building it.

I've added this as a step.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW, I suspect Chandler's ideal result would be leaving it on Compiler Explorer, just not building new versions.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No strong opinion TBH. Whatever is easiest.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I will file an issue with them to discuss it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi folks, we're fine with keeping the existing explorer versions. Plus it means old links won't break even though the upstream explorer is gone.

danakj and others added 3 commits April 8, 2025 13:59
Co-authored-by: Jon Ross-Perkins <[email protected]>
Co-authored-by: Jon Ross-Perkins <[email protected]>
@carbon-language carbon-language deleted a comment from CarbonInfraBot Apr 8, 2025
[on the main branch](https://docs.github.com/en/search-github/github-code-search/understanding-github-code-search-syntax#using-qualifiers)
of a repository, so the `trunk` branch for the `carbon-lang` repository. To
maintain searchability, the explorer codebase must either remain on `trunk` in
`carbon-lang` or in a sibling repository.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be worth noting here that github search does appear to work in archived repositories.

Copy link
Contributor

@chandlerc chandlerc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving for leads.

Good to mention the note from @zygoloid and record whatever the plan is with compiler explorer, but neither seem blocking here.

@danakj
Copy link
Contributor Author

danakj commented Apr 9, 2025

Filed compiler-explorer/compiler-explorer#7550 to discuss with the compiler-explorer team

Merged via the queue into carbon-language:trunk with commit 20444c0 Apr 9, 2025
8 checks passed
@danakj danakj deleted the proposal-explorer branch April 9, 2025 13:39
danakj added a commit to danakj/compiler-workflows that referenced this pull request Apr 22, 2025
The carbon-explorer is frozen and has been moved out of the
main carbon-lang repo. We can keep serving an old build, but
there's no need to keep building it from the archived repo.

See #7550 and carbon-language/carbon-lang#5270
dkm pushed a commit to compiler-explorer/compiler-workflows that referenced this pull request Apr 22, 2025
The carbon-explorer is frozen and has been moved out of the
main carbon-lang repo. We can keep serving an old build, but
there's no need to keep building it from the archived repo.

See #7550 and carbon-language/carbon-lang#5270
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal rfc Proposal with request-for-comment sent out proposal A proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants