Uh oh!
There was an error while loading. Please reload this page.
Codegen for ports and channels - #279
Closed
brson wants to merge 9 commits into
Closed
Conversation
…ustc, but not in rustboot
graydon
commented
Mar 22, 2011
Contributor
Integrated. |
keeperofdakeys pushed a commit
to keeperofdakeys/rust
that referenced
this pull request
Dec 12, 2017
unix: Add PIPE_BUF for bsd and notbsd This is the maximum size of guaranteed-atomic writes to a pipe.
kazcw pushed a commit
to kazcw/rust
that referenced
this pull request
Oct 23, 2018
* Migrate `i686::sse` to vendor types * Migrate `i686::sse2` to vendor types * Migrate i686::sse41 to vendor types * Migrate i686::sse42 to vendor types
Aaron1011 pushed a commit
to Aaron1011/rust
that referenced
this pull request
Oct 26, 2020
gi-dellav pushed a commit
to gi-dellav/rust
that referenced
this pull request
Dec 9, 2021
Added new GH actions CI
antoyo added a commit
to antoyo/rust
that referenced
this pull request
Jun 19, 2023
Regen intrinsics with latest LLVM version
celinval pushed a commit
to celinval/rust-dev
that referenced
this pull request
Jun 4, 2024
…ust-lang#279) * Correct check for vtable pointer type * Comment
noscripter pushed a commit
to noscripter/rust
that referenced
this pull request
Sep 8, 2025
U007D pushed a commit
to U007D/rust-mos
that referenced
this pull request
Aug 21, 2026
280: Fixed cast expression parsing in ra_syntax. r=matklad a=ruabmbua Fixesrust-lang#279 Related to rust-lang/rust-analyzer#273 The cast expression expected any type via types::type_() function, but the language spec does only allow TypeNoBounds (types without direct extra bounds via `+`). **Example:** ```rust fn test() { 6i8 as i32 + 5; } ``` This fails, because the types::type_() function which should parse the type after the as keyword is greedy, and takes the plus sign after path types as extra type bounds. My proposed fix is to replace the not implemented `type_no_plus()` just calls (`type_()`) function, which is used at several places. The replacement is `type_with_bounds_cond(p: &mut Parser, allow_bounds: bool)`, which passes the condition to relevant sub-parsers. This function is then called by `type_()` and the new public `type_no_bounds()`. Co-authored-by: Roland Ruckerbauer <roland.rucky@gmail.com>
U007D pushed a commit
to U007D/rust-mos
that referenced
this pull request
Aug 21, 2026
383: Bump failure from 0.1.3 to 0.1.4 r=DJMcNab a=dependabot[bot] Bumps [failure](https://github.com/rust-lang-nursery/failure) from 0.1.3 to 0.1.4. <details> <summary>Changelog</summary> *Sourced from [failure's changelog](https://github.com/rust-lang-nursery/failure/blob/master/RELEASES.md).* > # Version 0.1.4 > > - Improved error reporting of the derive feature > - Resolved a potential internal ambiguity when using the backtrace feature > that prevented backtrace from improving an upstream API. > - Changed the bounds on std error compat conversions through the From trait > to take Sync and Send into account. </details> <details> <summary>Commits</summary> - [`70b98e6`](rust-lang-deprecated/failure@70b98e6) 0.1.4 - [`937fb70`](rust-lang-deprecated/failure@937fb70) Add Sync and Send as failure::Error supports them. ([rust-lang#283](https://github-redirect.dependabot.com/rust-lang-nursery/failure/issues/283)) - [`15b6798`](rust-lang-deprecated/failure@15b6798) Improving procmacro error reporting - [`22bfd31`](rust-lang-deprecated/failure@22bfd31) support trailing commas in macros ([rust-lang#273](https://github-redirect.dependabot.com/rust-lang-nursery/failure/issues/273)) - [`26fc6eb`](rust-lang-deprecated/failure@26fc6eb) Future proof debug formatting. Fixes [rust-lang#279](https://github-redirect.dependabot.com/rust-lang-nursery/failure/issues/279) - [`0f89723`](rust-lang-deprecated/failure@0f89723) Reformat for latest rustfmt - [`8f8f92f`](rust-lang-deprecated/failure@8f8f92f) Update metadata to point to new docs - See full diff in [compare view](rust-lang-deprecated/failure@0.1.3...0.1.4) </details> <br /> [](https://dependabot.com/compatibility-score.html?dependency-name=failure&package-manager=cargo&previous-version=0.1.3&new-version=0.1.4) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot. </details> Co-authored-by: dependabot[bot] <support@dependabot.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This patch set implements code generation for ports and channels. I think this is all pretty nice - the only thing I'm really concerned about is the refcounting. From what I can tell the refcounts are working correctly; I just don't exactly understand why. I expected trans_recv to require a cleanup for the received data but it has thus far rejected my efforts to do so.
I'm beginning to understand what's going on in trans.rs, but please give it a close look and see if there's anything I can improve.
Next is implementing local declarations with receive, e.g. "let int x <- p", then on to spawning tasks.