Skip to content

relicense shootout-nbody.rs to the shootout license #17073

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

Closed
TeXitoi opened this issue Sep 7, 2014 · 2 comments · Fixed by #17077
Closed

relicense shootout-nbody.rs to the shootout license #17073

TeXitoi opened this issue Sep 7, 2014 · 2 comments · Fixed by #17077

Comments

@TeXitoi
Copy link
Contributor

TeXitoi commented Sep 7, 2014

See #14248

I propose to change the license of shootout-nbody.rs

Non trivial contributors:

Contributors appearing in git blame that are trivial (except artifacts as empty lines):

Contributors with removed and trivial contributions are not considered.

For the persons that are not in "OK" state, please respond to this issue saying:

I agree to relicense any previous contributions to http://github.com/rust-lang/rust according to the term of the Computer Language Benchmarks Game license (http://benchmarksgame.alioth.debian.org/license.php)

Then, I'll propose the corresponding PR.

Thanks.

@thestinger
Copy link
Contributor

I agree to relicense any previous contributions to http://github.com/rust-lang/rust according to the term of the Computer Language Benchmarks Game license (http://benchmarksgame.alioth.debian.org/license.php)

@willingc
Copy link
Contributor

willingc commented Sep 7, 2014

I agree to relicense any previous contributions to
http://github.com/rust-lang/rust https://github.com/rust-lang/rust
according to the term of the Computer Language Benchmarks Game license
(http://benchmarksgame.alioth.debian.org/license.php)

On 07/09/2014 09:59, Daniel Micay wrote:

I agree to relicense any previous contributions to
http://github.com/rust-lang/rust https://github.com/rust-lang/rust
according to the term of the Computer Language Benchmarks Game license
(http://benchmarksgame.alioth.debian.org/license.php)


Reply to this email directly or view it on GitHub
#17073 (comment).

Carol Willing
Developer | Willing Consulting
+1 760 456 9366 | https://willingconsulting.com

TeXitoi added a commit to TeXitoi/rust that referenced this issue Sep 7, 2014
lnicola pushed a commit to lnicola/rust that referenced this issue Apr 20, 2024
Better inline preview for postfix completion

Better inline preview for postfix completion, a proper implementation of c5686c8.

Here editors may filter completion item with the text within `delete_range`, so we need to include the `receiver text` in the `lookup` (aka `FilterText` in LSP spec) for editors to find the completion item. (See rust-lang/rust-analyzer#17036 (comment), Thanks to [pascalkuthe](https://github.com/pascalkuthe))
lnicola pushed a commit to lnicola/rust that referenced this issue Apr 20, 2024
lnicola pushed a commit to lnicola/rust that referenced this issue Apr 20, 2024
…kril

Revert rust-lang#17073: Better inline preview for postfix completion

See discussion on rust-lang/rust-analyzer#17077, but I strongly suspect that the changes to the `TextEdit` ranges caused VS Code's autocomplete to prefer the snippets over method completions. I explain why I think that [here](rust-lang/rust-analyzer#17077 (comment)).
lnicola pushed a commit to lnicola/rust that referenced this issue Apr 20, 2024
Better inline preview for postfix completion

Better inline preview for postfix completion, a proper implementation of c5686c8.

Here editors may filter completion item with the text within `delete_range`, so we need to include the `receiver text` in the `lookup` (aka `FilterText` in LSP spec) for editors to find the completion item. (See rust-lang/rust-analyzer#17036 (comment), Thanks to [pascalkuthe](https://github.com/pascalkuthe))
lnicola pushed a commit to lnicola/rust that referenced this issue Apr 20, 2024
lnicola pushed a commit to lnicola/rust that referenced this issue Apr 20, 2024
…kril

Revert rust-lang#17073: Better inline preview for postfix completion

See discussion on rust-lang/rust-analyzer#17077, but I strongly suspect that the changes to the `TextEdit` ranges caused VS Code's autocomplete to prefer the snippets over method completions. I explain why I think that [here](rust-lang/rust-analyzer#17077 (comment)).
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 a pull request may close this issue.

3 participants