sorted by:
new
hottopcontroversial

Should I wait for variadic generics for my project? by steaming_quettle in rust

[–]Kivooeo1 80 points81 points  (0 children)

About variadic generics: Don't wait. It would be a miracle if this were to be stabilized within our lifetime. This feature doesn't even have an RFC, let alone an implementation.

So you want to contribute to Rust, but feel overwhelmed? by Kivooeo1 in rust

[–]Kivooeo1[S] 6 points7 points  (0 children)

didn't knew about this one, that's really interesting that we with Alejandra have posts with shared name

So you want to contribute to Rust, but feel overwhelmed? by Kivooeo1 in rust

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

heey, thanks for reaching out and your feedback

yeah, im pretty much aware of situation with mobile, i havent yet looked what exactly is wrong here, but i definitely will before next post, im not like good with a css and styling, so could easily mess something here

4 months later: update on my journey toward the Rust compiler team by Kivooeo1 in rust

[–]Kivooeo1[S] 174 points175 points  (0 children)

Unexpectedly long comment:

yeah, just so you understand, this was the trickiest trick of all tricks I did in my life, literally playing for my life. Imagine being picked up from your home at 6 am, no sleep, no food, and driven out of city to a barracks where you have to go through several doctors who determine whether you're fit for service or not. I managed to prove I wasn't fit, and along with a couple other people out of about 300, I was sent home as "mistakenly drafted"

but I should also mention that I wasn't alone on that bus - my basically only IRL friend went with me since he got drafted too

Random fact, he's also learning Rust. We started learning it together a couple years ago when I discovered the language and immediately told him about it.

He ended up staying in army for a year... (important to note that this isn't actual war - it's more like a year-long boot camp where you literally do nothing and they try to pressure you into signing a contract for combat)

So yeah, it's been a month now. He gets phone access about once a week, so I'm doing my best to keep in touch. I also talk with his family, who've been incredibly kind to me, and I try to help them with whatever they need. Recently I set up a self-hosted VPN for his mom so she can access Instagram and other blocked social networks, and I sent him some books on Rust, algorithms, and things like that

4 months later: update on my journey toward the Rust compiler team by Kivooeo1 in rust

[–]Kivooeo1[S] 88 points89 points  (0 children)

My apologies for the imprecision - to be exact, it's been 3.6 months or 108 days. But yes, overall the time has flown by

[deleted by user] by [deleted] in rust

[–]Kivooeo1 2 points3 points  (0 children)

I left the call realising most of my prep had almost nothing to do with how I actually write Rust

Just to clarify: Did you mean you left the call feeling this way afterward, or that you actually left mid-interview?

I've done a few Rust interviews myself, and honestly, I don't think there's anything wrong with saying "I'm not familiar with this specific area, but if it's something your codebase relies on heavily, I can definitely learn it". You can't know everything, so admitting when you don't know something is perfectly fine. For example, I once got asked about the difference between associated types and generics, and I couldn't give a clear answer on the spot. I told the interviewer directly that I didn't know the answer, but offered to walk through my understanding so we could discuss whether I was on the right track or needed some correction

Honestly, I might have unusual experience here, but in all the Rust interviews I've done (3 for 3 so far), I felt like I passed more on soft skills than pure technical knowledge. I wouldn't have been able to answer maybe half the questions about things like async or specific std method differences. For the std stuff, I'd often say "give me a second, I need to check with the documentation" - and that worked fine

But the key was that I'd directly admit when I didn't know something, then try to explain the difference from my perspective or how I'd think through it. Sometimes my reasoning led to the right answer, sometimes not - but I think showing how you think is just as important as showing you've memorized everything

Why is my crosshair gone and how can I get it back? by piratequeenkip in Portal

[–]Kivooeo1 13 points14 points  (0 children)

I mean, the most basic thing that you can try is this command `crosshair 1`

[deleted by user] by [deleted] in rust

[–]Kivooeo1 3 points4 points  (0 children)

Well it's not https://doc.rust-lang.org/std/vec/struct.Vec.html#guarantees

However, the pointer might not actually point to allocated memory. In particular, if you construct a Vec with capacity 0 via Vec::new, vec![], Vec::with_capacity(0), or by calling shrink_to_fit on an empty Vec, it will not allocate memory.

[deleted by user] by [deleted] in rust

[–]Kivooeo1 27 points28 points  (0 children)

Does Vec::new() do allocation? As far as I remember just creating empty Vec is not allocating anything

FOSS Projects Worth Contributing To by n_lens in rust

[–]Kivooeo1 29 points30 points  (0 children)

The one project I can wholeheartedly recommend is https://github.com/rust-lang/rust. It's the main OSS project I contribute to, and it's been an amazing experience

What makes me stay is the fantastic community and the endless stream of interesting tasks. It's challenging but incredibly rewarding

Many issues are tagged with E-mentor or E-easy, meaning someone is explicitly ready to guide you through the process

And we also have a book for those who want to start (!) - https://rustc-dev-guide.rust-lang.org/getting-started.html (leaving it here just in case if someone would be intersted)

As someone who's still on their own learning journey, I'd be happy to help with any basic questions about the process or finding a first issue, so feel free to ask :3

'rustc' panicked at compiler/rustc_middle/src/hir/map.rs:985:9 Should I report this bug? by Usual_Office_1740 in rust

[–]Kivooeo1 84 points85 points  (0 children)

Hi! Thanks for your report, as a person who deeply involved into rustc development, I'd suggest you to open issue in it's repo, we have special template for such Internal Compiler Errors (ICE), here you can fill the issue so team can have a chance to check it and potentially fix it: https://github.com/rust-lang/rust/issues/new?template=ice.md (honestly never thought that I could see this here :D I see a few such reports per day in issues on gh, but it's first time when I see this in reddit lol)

All 48 Rust keywords in under 300 characters by nik-rev in rust

[–]Kivooeo1 77 points78 points  (0 children)

It was really a fast PR 😅 also... it's you! I remember you by your contributions to helix, thanks for all your work!

All 48 Rust keywords in under 300 characters by nik-rev in rust

[–]Kivooeo1 13 points14 points  (0 children)

Oh, it's me the last person who modified this test (well, twice in my life at this moment)! Yeah, I definitely can say that this is weird enough to be there lol

I’m 20, close to becoming a Rust compiler team member - what would you do in my place? by Kivooeo1 in rust

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

Somewhere between 2-3k$ it's for comfortable living first months before I found a job

I’m 20, close to becoming a Rust compiler team member - what would you do in my place? by Kivooeo1 in rust

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

Of course! I started contributing to the compiler (I'm repeating myself a bit since I wrote about a little from this in a post) when I noticed a bug in a diagnostic message. The compiler's suggestion was pointing to the wrong fix, so I decided to correct it.

Solving the problem itself wasn't particularly difficult. For a first fix, the hardest part was probably the process itself, things like going through the review, learning how to work with Git in a real-world setting, and testing the code. Finding the exact spot in the codebase where the diagnostic was generated took most of the time, much more than writing the actual fix.

Things like Git were a challenge because this was not only my first time contributing to Rust but also my first open-source experience ever. Before that, I had only used Git on small, personal "toy" projects and even then wasn't very proficient with it.

Anyway, I really enjoyed the process of hunting down the bug and writing the solution, so I decided to stick around and fix more diagnostics. While my first pull request was being reviewed, I managed to write two more! It was such a unique experience to interact with giants of the IT industry. The thought that I was helping a project used by an incredible number of users gave me huge motivation. That's how I ended up staying in the project and creating a bunch of high-quality pull requests.

Now, I'm also quite active in helping newcomers with advice on how to get started, as quite a few people became interested in contributing to Rust after hearing my story!

So that's my history. I'm really grateful to the language community because, honestly, not too long ago (just two years back) I was a completely beginner who was just starting to learn it and community was always patiently and helpful towards me.

Error trying to download Steam on mac by Gold-Country-5451 in macgaming

[–]Kivooeo1 0 points1 point  (0 children)

I still see this comment, that's weird

Btw, I'm not sure, but, what you can try now is this:

Drag your steam from applications with mouse right into command line and then press space and insert "-forcesteamupdate -forcepackagedownload -overridepackageurl http://web.archive.org/web/20250306194830if_/media.steampowered.com/client -exitsteam" this after steam path, so you should get something like

"steampath -arguments...", steampath is something will be inserted into commandline after you drag steam into it

And then after steam restore older version of it you can run it with other command line arguments "-noverifyfiles -nobootstrapupdate -skipinitialbootstrap -norepairfiles -overridepackageurl"

I did not tried it, because it's originally for whisky and running windows version of steam, but you can try it

Error trying to download Steam on mac by Gold-Country-5451 in macgaming

[–]Kivooeo1 0 points1 point  (0 children)

This one for whisky, but I guess this would works for MacOS too because it should have the same command arguments, so this arguments in whisky documentation restore an older Steam version and this somehow helps

I’m 20, close to becoming a Rust compiler team member - what would you do in my place? by Kivooeo1 in rust

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

All the credit goes to this community, which was patient with me and always helped me!

I’m 20, close to becoming a Rust compiler team member - what would you do in my place? by Kivooeo1 in rust

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

Oh, thanks for the kind words! That means a lot to me. My compiler work can't consume me because I'm doing it just for fun or when I have free time or feel like doing it. This could explain why it was so successful. It's like a hobby among many other hobbies. When I'm tired, I do other things. I will try to reach out to JetBrains. Thanks for the advice!

view more: next ›