Skip to content

Add impl Show for &Show #15281

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 1 commit into from
Jul 1, 2014
Merged

Add impl Show for &Show #15281

merged 1 commit into from
Jul 1, 2014

Conversation

alexcrichton
Copy link
Member

This makes printing a Show trait object much easier.

This makes printing a `Show` trait object much easier.
bors added a commit that referenced this pull request Jul 1, 2014
This makes printing a `Show` trait object much easier.
@bors bors closed this Jul 1, 2014
@bors bors merged commit 8bdc4b5 into rust-lang:master Jul 1, 2014
@alexcrichton alexcrichton deleted the show-for-show branch July 4, 2014 00:20
bors added a commit to rust-lang-ci/rust that referenced this pull request Jul 24, 2023
…cola

editor/code: Break down CI steps to know what is failing easily

This do the thing I mentioned in rust-lang/rust-analyzer#15265 (comment)

This aims to improve CI status check more readable.

I tried to use [`jobs.<job_id>.if`](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idif) to make the configuration
more shortly once.

But it could not fire the `end-success` or `end-failure` status if some jobs in the workflow were skipped. This causes an integration problem with bors.

By their reasons, this patch still uses `jobs.<job_id>.steps[*].if`.

---

To do this change, we reorganize npm-script.

| previous           | after                                  |
|--------------------|----------------------------------------|
| `npm run lint`     | `npm run lint && npm run format:check` |
| `npm run fix`      | `npm run lint:fix && npm run format`   |

The previous `npm run fix` sometimes does not complete fix automatically because ESLint's autofix doees not follow prettier's formatting. So we need to run `npm run lint:fix && npm run format` by this order.
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 this pull request may close these issues.

3 participants