profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/fee1-dead/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
fee1-dead 15 to be free, and not broken

java-deobfuscator/deobfuscator 925

The real deal

x4e/binfix 28

Java Bytecode Deobfuscation

x4e/classfile-rs 19

JVM classfile parser and writer for Rust

fee1-dead/coffer 6

A lightweight and fast Rust library for reading and writing Java classes.

fee1-dead/EventListener 4

Simple, Multiplatform event system with Kotlin's lambda

fee1-dead/blog 1

"rustdoc themed SSG" + my blog

fee1-dead/brainfuck-rs 1

Convert b****fuck to rust.

fee1-dead/myscale 1

myScale but improved

fee1-dead/asmtools 0

https://wiki.openjdk.java.net/display/CodeTools/asmtools

pull request commentrust-lang/rust

constified implementations of `Default`

Ping @rust-lang/libs-api

fee1-dead

comment created time in 5 hours

push eventfee1-dead/rust

Jon Gjengset

commit sha 3b2b5b2914d40aa011d189bfe546084cdee53dbe

Remove P: Unpin bound on impl Future for Pin The `Unpin` bound was originally added in #56939 following the recommendation of @withoutboats in https://github.com/rust-lang/rust/issues/55766#issue-378417538 That comment does not give explicit justification for why the bound should be added. The relevant context was: > [ ] Remove `impl<P> Unpin for Pin<P>` > > This impl is not justified by our standard justification for unpin > impls: there is no pointer direction between `Pin<P>` and `P`. Its > usefulness is covered by the impls for pointers themselves. > > This futures impl (link to the impl changed in this PR) will need to > change to add a `P: Unpin` bound. The decision to remove the unconditional impl of `Unpin for Pin` is sound (these days there is just an auto-impl for when `P: Unpin`). But, I think the decision to also add the `Unpin` bound for `impl Future` may have been unnecessary. Or if that's not the case, I'd be very interested to have the argument for why written down somewhere. The bound _appears_ to not be needed, since the presence of a `Pin<P>` should indicate that it's safe to project to `Pin<&mut P::Target>` just like for `Pin::as_mut`.

view details

Joshua Nelson

commit sha d67f1a48efbcdc689c69b6218ec55b541ebf8c7a

Update log to 0.4.14 This avoids the following warning: ``` warning: trailing semicolon in macro used in expression position --> /home/joshua/.local/lib/cargo/registry/src/github.com-1ecc6299db9ec823/log-0.4.11/src/macros.rs:152:45 | 147 | / macro_rules! debug { 148 | | (target: $target:expr, $($arg:tt)+) => ( 149 | | log!(target: $target, $crate::Level::Debug, $($arg)+); 150 | | ); 151 | | ($($arg:tt)+) => ( 152 | | log!($crate::Level::Debug, $($arg)+); | | ^ 153 | | ) 154 | | } | |_- in this expansion of `debug!` | ::: src/tools/rustfmt/src/modules/visitor.rs:36:23 | 36 | Err(e) => debug!("{}", e), | --------------- in this macro invocation | = note: requested on the command line with `-W semicolon-in-expressions-from-macros` = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813> ```

view details

jedel1043

commit sha e243be6adad16ad65c3349e476d528d1f416ed59

Allow formatting `Anonymous{Struct, Union}` declarations

view details

Jon Gjengset

commit sha ac658e106653a5aa048eec158b66c9e0485b952b

Merge branch 'master' into no-unpin-in-pin-future-impl

view details

Ryan Levick

commit sha 58c63cf8dec2b7d97667932c17248f774dd6e1ab

Add support for using qualified paths with structs in expression and pattern position.

view details

Fabian Wolff

commit sha 74d1bd21c78765712612afdd5eab3efa00757064

Use more precise span for E0282 in cast expressions

view details

Jon Gjengset

commit sha b5e5a182caa6efb7359978a6ff596f403cb4c099

Update library/core/src/pin.rs Co-authored-by: Ralf Jung <post@ralfj.de>

view details

Yuki Okushi

commit sha 1e2258ffa949bf4d273259e78d326857c0b2bb3d

Use `AttrVec` for `Arm`, `FieldDef`, and `Variant`

view details

Caleb Cartwright

commit sha 2608f2c63bbc565cffd02514c997511ac31f74aa

fix(rustfmt): load nested out-of-line mods correctly

view details

Christiaan Dirkx

commit sha a26237e634be7f94dbd40cc1204514f2b4c380d2

Remove `Ipv4Addr::is_ietf_protocol_assignment`

view details

Alexander Melentyev

commit sha 71f01d197411fc7a9b3509cbf566720eabdf8d92

Delete spaces

view details

Yuki Okushi

commit sha d13020cd3168483449d22eb1f1246e2bb8ae197d

Rollup merge of #86274 - alexander-melentyev:spaces, r=bjorn3 Spaces

view details

Yuki Okushi

commit sha 0b8a26f5078d67923794956f3a502a5f5bb76e60

Rollup merge of #86424 - calebcartwright:rustfmt-mod-resolution, r=Mark-Simulacrum rustfmt: load nested out-of-line mods correctly This should address https://github.com/rust-lang/rustfmt/issues/4874 r? `@Mark-Simulacrum` Decided to make the change directly in tree here for expediency/to minimize any potential backporting issues, and because there's some subtree sync items I need to get resolved before pulling from r-l/rustfmt

view details

Jacob Pratt

commit sha 5d851309958735e875dbd4361e97a1996cc83d4d

Partially stabilize `const_slice_first_last`

view details

Marcus Calhoun-Lopez

commit sha 956fd10660e836ac4602527f7297aa68b24eca17

Cross compiling rustc_llvm on Darwin requires zlib.

view details

Joshua Nelson

commit sha 33acc960f78cfde092a4e720c01896fbff86cdc8

Document rustfmt on nightly-rustc The recursion_limit attribute avoids the following error: ``` error[E0275]: overflow evaluating the requirement `std::ptr::Unique<rustc_ast::Pat>: std::marker::Send` | = help: consider adding a `#![recursion_limit="256"]` attribute to your crate (`rustfmt_nightly`) ```

view details

Christiaan Dirkx

commit sha c93cb40b90b5f862bf448136cbe608f43ae0f62f

Move `os_str_bytes` to `sys::unix` and reuse it on other platforms.

view details

Aris Merchant

commit sha f2c0f29248fa6f6d2c8d71fdfa2dfb86088dc4c7

Change env var getters to error recoverably Before this, `std`'s env var getter functions would panic on receiving certain invalid inputs. This commit makes them return a `None` or `Err` instead.

view details

Aris Merchant

commit sha d26e01e9df416304f7d0cc425bd0290560e12fae

Add test to prevent regression

view details

Aris Merchant

commit sha a12107afaaa634cd7352d3828caef89a975299bb

Make `getenv` return an Option instead of a Result

view details

push time in 8 hours

push eventfee1-dead/rust

Deadbeef

commit sha 5510d43f08a16fc364271db4999275f25e5d5627

Constified `Default` implementations

view details

push time in 8 hours

pull request commentrust-lang/rust

Constify ?-operator for Result and Option

  = note: conflicting implementation in crate `core`:
          - impl<T, U> Into<U> for T
            where const U: From<T>;

That might be a bug that I need to fix...

usbalbin

comment created time in 8 hours

Pull request review commentrust-lang/rust

Fixed #85845: Added a note in E0369 if the missing trait is PartialEq

 fn suggest_impl_missing(err: &mut DiagnosticBuilder<'_>, ty: Ty<'_>, missing_tra                 "an implementation of `{}` might be missing for `{}`",                 missing_trait, ty             ));+            // This checks if the missing trait is PartialEq to suggest adding a derive+            if missing_trait.ends_with("PartialEq") {+                err.note(&format!(

Because you want to suggest adding a derive to the type being compared here. So you use the span of the original definition and add a #[derive(PartialEq)] on top of it, or add PartialEq to the existing derive.

ccgauche

comment created time in 20 hours

PullRequestReviewEvent

push eventfee1-dead/rust

Deadbeef

commit sha 4f01bd886e713675469b97be4dc2eb70c4dd6547

Do not lint if in macro expansion

view details

push time in a day

push eventfee1-dead/rust

push time in a day

push eventfee1-dead/rust

Deadbeef

commit sha 9ecf51d8c7a7a2f278cc1b3af2618afce49cac8e

Readd const_fn_union feature

view details

push time in a day

PR closed rust-lang/rust

Bump bootstrap compiler version to 1.55 S-waiting-on-review

This PR is #87622 with the const_fn_union feature attributes readded, as it looks like it wasn't backported to beta.

r? @Mark-Simulacrum cc @pietroalbini

(I don't have the permission to r= the PR)

+7 -30

2 comments

16 changed files

fee1-dead

pr closed time in 2 days

PR opened rust-lang/rust

Bump bootstrap compiler version to 1.55

This PR is #87622 with the const_fn_union feature attributes readded, as it looks like it wasn't backported to beta.

r? @Mark-Simulacrum cc @pietroalbini

(I don't have the permission to r= the PR)

+7 -30

0 comment

16 changed files

pr created time in 2 days

create barnchfee1-dead/rust

branch : bump-bootstrap

created branch time in 2 days

push eventfee1-dead/rust

Deadbeef

commit sha 1d3f34e86418c124919b81186cf2ada84626f916

Remove the lint from clippy

view details

push time in 2 days

push eventfee1-dead/rust

Deadbeef

commit sha 58bb875d3b8face677e2b2eb0a45d45bb364dec7

Remove the lint from clippy

view details

push time in 2 days

push eventfee1-dead/rust

Deadbeef

commit sha ad3d04bf03cb877ac24dcb30e83900104639149a

Fix the lint for ui tests

view details

push time in 3 days

push eventfee1-dead/rust

Deadbeef

commit sha ebb23552481a1057d5898836fa17410dbb87c09e

Fix the lint for ui tests

view details

push time in 3 days

push eventfee1-dead/rust

Deadbeef

commit sha c8514ccdcb46701b7554f1f309b51e4095b57985

Fix the lint for ui tests

view details

push time in 3 days

push eventfee1-dead/rust

Jon Gjengset

commit sha 3b2b5b2914d40aa011d189bfe546084cdee53dbe

Remove P: Unpin bound on impl Future for Pin The `Unpin` bound was originally added in #56939 following the recommendation of @withoutboats in https://github.com/rust-lang/rust/issues/55766#issue-378417538 That comment does not give explicit justification for why the bound should be added. The relevant context was: > [ ] Remove `impl<P> Unpin for Pin<P>` > > This impl is not justified by our standard justification for unpin > impls: there is no pointer direction between `Pin<P>` and `P`. Its > usefulness is covered by the impls for pointers themselves. > > This futures impl (link to the impl changed in this PR) will need to > change to add a `P: Unpin` bound. The decision to remove the unconditional impl of `Unpin for Pin` is sound (these days there is just an auto-impl for when `P: Unpin`). But, I think the decision to also add the `Unpin` bound for `impl Future` may have been unnecessary. Or if that's not the case, I'd be very interested to have the argument for why written down somewhere. The bound _appears_ to not be needed, since the presence of a `Pin<P>` should indicate that it's safe to project to `Pin<&mut P::Target>` just like for `Pin::as_mut`.

view details

Joshua Nelson

commit sha 23bbd65d968ef385fa7a7cd90ea8252bd78081b1

Remove unstable `--pretty` flag It doesn't do anything `--unpretty` doesn't, and due to a bug, also didn't show up in `--help`. I don't think there's any reason to keep it around, I haven't seen anyone using it.

view details

Jon Gjengset

commit sha ac658e106653a5aa048eec158b66c9e0485b952b

Merge branch 'master' into no-unpin-in-pin-future-impl

view details

marcusdunn

commit sha ef65e091dbf4063c019d3429789f3a0d0c73d098

added unstable-book entry for bindings_after_at

view details

marcusdunn

commit sha 2d74cd255d599436675b2f67ad3ad1956dc9f02a

made doc entry more consistant with others

view details

marcusdunn

commit sha 751ddb7eb2d585c39d4461a333c9b3408114fcfa

updated the feature-gate listing

view details

marcusdunn

commit sha b908905b3defa075d08661dc5916219a870b4856

changeded bindings_after_at from active to accepted

view details

marcusdunn

commit sha a32d2b43a2ac802a3fc4c601e07828a4eace89a8

removed uses of feature gate

view details

marcusdunn

commit sha 21dee3cbf843d1d897da6ace5143f5a14d475dbe

removed conditional check on bindings_after_at and resulting dead code

view details

marcusdunn

commit sha a49a6827afeaaeca48f36d1fd0ac4c07de053602

removed more uses of feature gate

view details

marcusdunn

commit sha a11c8e7ff348fa5747b7a06390d95254627f8e0e

replaced feature-gate use with cfg_attr

view details

marcusdunn

commit sha 2d82b4a2b7ea6612b937dc4457f73409cd967e5d

removed entry for bindings after at in unstable book

view details

marcusdunn

commit sha 43d8854b560d4ad6750c2057e922f20b47221b8b

removed unneeded brackets on import

view details

marcusdunn

commit sha efc5714e59608b6f9f50481aca41a3ffa6160ea4

updated line #'s on ui tests and removed feature flag test

view details

marcusdunn

commit sha 5f9e33f680a4e8caac9f02bb0908d031a2dbaca0

removed ref to bindings_after_at

view details

marcusdunn

commit sha c2af4cb9a3ce0c6a5ea9c52ac8988715842db4d7

added back bindings_after_at as a cfg_attr

view details

Fabian Wolff

commit sha 74d1bd21c78765712612afdd5eab3efa00757064

Use more precise span for E0282 in cast expressions

view details

Jon Gjengset

commit sha b5e5a182caa6efb7359978a6ff596f403cb4c099

Update library/core/src/pin.rs Co-authored-by: Ralf Jung <post@ralfj.de>

view details

Marcus Calhoun-Lopez

commit sha 956fd10660e836ac4602527f7297aa68b24eca17

Cross compiling rustc_llvm on Darwin requires zlib.

view details

Esteban Küber

commit sha 8ea53624c9a2c4aa6bd207dd25b8d2b19610c99f

Avoid ICE on type error recovery Fix #86756

view details

push time in 3 days

push eventfee1-dead/rust

Deadbeef

commit sha 499bf0099ac1d8000b5cdf146bebf924c9e95fa0

Fix the lint for ui tests

view details

push time in 3 days

push eventfee1-dead/rust

Deadbeef

commit sha 0479460b457e99442480045411dfbb895325d289

Rename the lint

view details

Deadbeef

commit sha e5bf023283ca67aefeb7cdd35bdbfe64d5eac8f0

Fix the lint for ui tests

view details

push time in 3 days

pull request commentrust-lang/rust

Port clippy lint `redundant_field_names` to compiler

Can we put this in the nonstandard-style group?

I don't think so because AFAIK that group is only used for lints with nonstandard naming conventions.

fee1-dead

comment created time in 4 days

issue commentrust-lang/rust

Generic functions in `impl const Trait` seem to have non-const trait-bounds

This has been fixed.

Cryptjar

comment created time in 4 days

pull request commentrust-lang/rust

Rollup of 9 pull requests

I just joined a working group and I don't know how I can join a team with such permission...

fee1-dead

comment created time in 4 days

delete branch fee1-dead/rust

delete branch : rollup-xmlm41q

delete time in 4 days

pull request commentrust-lang/rust

Rollup of 10 pull requests

Sorry for interrupting this because I just found a previous discussion to do a crater run first. See this comment for details, so I guess you should close this in favor of #87595.

GuillaumeGomez

comment created time in 4 days

PR opened rust-lang/rust

Rollup of 9 pull requests

Successful merges:

  • #85901 (Bufwriter disassembly tweaks)
  • #87285 (Improve intra doc errors display)
  • #87385 (Make SEMICOLON_IN_EXPRESSIONS_FROM_MACROS warn by default)
  • #87483 (Mir borrowck does not generate lifetime variables for 'static lifetimes during opaque type resolution)
  • #87488 (Track caller of Vec::remove())
  • #87522 (Fix assert in diy_float)
  • #87553 (Fix typo in rustc_driver::version)
  • #87554 (2229: Discr should be read when PatKind is Range)
  • #87564 (min_type_alias_impl_trait is going to be removed in 1.56)

Failed merges:

r? @ghost @rustbot modify labels: rollup <!-- homu-ignore:start --> Create a similar rollup <!-- homu-ignore:end -->

+497 -179

0 comment

43 changed files

pr created time in 4 days

push eventfee1-dead/rust

Santiago Pastorino

commit sha cf5e48d944fcc068c7d9b55399684f7e3437628a

min_type_alias_impl_trait is going to be removed in 1.56

view details

fee1-dead

commit sha afd306628ce534bbdd17eb73b234fbfb42c18061

Rollup merge of #87564 - spastorino:adjust-min-tait-removed-version, r=jackh726 min_type_alias_impl_trait is going to be removed in 1.56 #87501 removed `min_type_alias_impl_trait` but meanwhile that PR was approved in homu queue, a new beta was cut so we need to bump the version because it won't be removed in 1.55. r? ``@oli-obk`` ``@bors`` rollup=always

view details

push time in 4 days

push eventfee1-dead/rust

Roxane

commit sha 9829efb892f7c249f2c889722a098e6a9b34f3fb

Range PatKind implies discr should be read

view details

Roxane

commit sha d380ed13043d52139b3c766a07edb93b891e2be6

fix nit

view details

fee1-dead

commit sha cee4f91f28edb3990c121af09701a1d3b03ccd34

Rollup merge of #87554 - sexxi-goose:fix-issue-87426, r=nikomatsakis 2229: Discr should be read when PatKind is Range This PR fixes an issue related to pattern matching in closures when Edition 2021 is enabled. - If any of the patterns the discr is being matched on is `PatKind::Range` then the discr should be read r? ``@nikomatsakis`` Closes https://github.com/rust-lang/rust/issues/87426

view details

push time in 4 days

push eventfee1-dead/rust

bjorn3

commit sha cd6c0e4e3b71cffd6e577146cbf989ad6ba29c63

Fix typo in rustc_driver::version This caused rustc -Zcodegen-backend=foo.so -vV to look for oo.so instead of foo.so

view details

bjorn3

commit sha 2f6662da85d47ebf89432c910a496812e9e2db12

Use strip_prefix

view details

fee1-dead

commit sha 433e5a1760808fe6f960137b886fada395511537

Rollup merge of #87553 - bjorn3:fix_hotplug_codegen_version, r=wesleywiser Fix typo in rustc_driver::version This caused rustc `-Zcodegen-backend=foo.so -vV` to look for `oo.so` instead of `foo.so`

view details

push time in 4 days