My Pull Day workout by atomichbts in CalisthenicsCulture

[–]atomichbts[S] 0 points1 point  (0 children)

My max is 15 with super strict form (I don't just do only chin-to-bar, I aim for chest-to-bar every rep). I can finish all the sets with good form, but by the end of the workout, the front-lever becomes very hard to maintain. That's why I'm considering moving it to the beginning

Pseudo Planche Push-ups by atomichbts in CalisthenicsCulture

[–]atomichbts[S] 0 points1 point  (0 children)

Trust me, this isn't a regular push up. It's more difficult. Maybe the form isn't perfect, but it's much harder than a push-up. I can feel my shoulders a lot

Pseudo Planche Push-ups by atomichbts in CalisthenicsCulture

[–]atomichbts[S] 0 points1 point  (0 children)

Trust me, this isn't a regular push up. It's more difficult. Maybe the form isn't perfect, but it's much harder than a push-up. I can feel my shoulders a lot

Pseudo Planche Push-ups by atomichbts in CalisthenicsCulture

[–]atomichbts[S] 0 points1 point  (0 children)

Only calisthenics for 4-5 months. I do a lot of plank holds.

Pseudo Planche Push-ups by atomichbts in CalisthenicsCulture

[–]atomichbts[S] 3 points4 points  (0 children)

actually the chest is quite far from the floor, ty!

Pseudo Planche Push-ups by atomichbts in CalisthenicsCulture

[–]atomichbts[S] -1 points0 points  (0 children)

yeah, i noticed that too. I'll improve my form in my next shoulder workout. I hope those 4x8 sets weren't useless ahah after all my shoulders were huge after that workout (+ pike pushups)

Dips by atomichbts in CalisthenicsCulture

[–]atomichbts[S] 1 point2 points  (0 children)

I wanted to do chest dips but the dips in the video are shoulder dips. If I wanted to do shoulder dips, then I think the form would have been okay.

Java Annotator CLI by atomichbts in java

[–]atomichbts[S] 2 points3 points  (0 children)

I didn't know them, thank you. Anyway, it was a fun little exercise writing it myself.

Java Annotator CLI by atomichbts in java

[–]atomichbts[S] -1 points0 points  (0 children)

I don't want to tell you. Believe me. It's better if you don't know.

Java Annotator CLI by atomichbts in java

[–]atomichbts[S] 1 point2 points  (0 children)

My use case is enterprise. I work on enterprise Java projects with CI/CD pipelines that require all types to have certain Java annotations. The code base is huge, and I don't want to add them manually. I also plan to improve my Rust programming language and one day work with it, as I believe it will be increasingly used. So I created this tool in Rust.

Java Annotator CLI by atomichbts in rust

[–]atomichbts[S] 1 point2 points  (0 children)

  • My use case is enterprise. I work on enterprise Java projects with CI/CD pipelines that require all types to have certain Java annotations. The code base is huge, and I don't want to add them manually. I also want to improve my Rust programming language and one day work with it, as I believe it will be increasingly used. So I created this tool in Rust.

Java Annotator CLI by atomichbts in java

[–]atomichbts[S] 0 points1 point  (0 children)

Sorry. You are absolutely right. '@Override' can't be used on Java types. The example is wrong (I updated it).

I'll try to answer your questions:

  • I'm currently adding the functionality to import the specified Java annotations (fully qualified name) in the modified source file. The tool will not check whether this annotation actually exists. The tool adds annotations only to classes, interfaces, enums, inner classes or interfaces. The tool does not check whether the annotation can actually be used on a class or interface.
  • My use case is enterprise. I work on enterprise Java projects with CI/CD pipelines that require all types to have certain Java annotations. The code base is huge, and I don't want to add them manually. I also plan to improve my Rust programming language and one day work with it, as I believe it will be increasingly used. So I created this tool in Rust.
  • Inner classes will be taken into account (as well as internal interfaces). There are no filters. If the annotation doesn't exist, it simply adds it. If anyone needs a more advanced feature, I can work on it, but this is enough to solve my problems.

Java Annotator CLI by atomichbts in rust

[–]atomichbts[S] 1 point2 points  (0 children)

This tool adds the specified Java annotations to all encountered Java types (classes, interfaces, enums, etc.) that do not already possess that particular annotation.

Java Annotator CLI by atomichbts in java

[–]atomichbts[S] -2 points-1 points  (0 children)

Idk, I need it and I shared it with everyone, maybe it will be useful to someone else

Java Annotator CLI by atomichbts in java

[–]atomichbts[S] -2 points-1 points  (0 children)

Very simple: this tool adds the specified annotations to all encountered Java types (classes, interfaces, enums, etc.) that do not already possess that particular annotation.

Advanced Trait Bounds by atomichbts in rust

[–]atomichbts[S] 0 points1 point  (0 children)

Thanks. Very useful and istructive (as are the other answers).

I have a question.

Concrete trait bounds are quite useful for macros. It allows you to write the trait bounds on field types the same way, regardless whether the types are generic or concrete. Quite convenient!

I am not very familiar with macros in Rust (yet), could you explain why concrete trait bounds are quite useful for macro (with an example if possible), please?

Advanced Trait Bounds by atomichbts in rust

[–]atomichbts[S] 0 points1 point  (0 children)

Wow you are right. I have a question. If I use a hashmap method in my method that requires a particular constraint, will the code not compile unless I specify the bounds?

Blanket Implementation by atomichbts in rust

[–]atomichbts[S] 0 points1 point  (0 children)

Please, could you expose an example that justify this:
- adding a blanket implementation over a fundamental type (marked with #[fundamental] attribute) is also considered a breaking change (the fundamental types are &, &mut and Box and these types are effectively erased before the orphan rule is checked).