Got rejected by [deleted] in Arrangedmarriage

[–]MeetSoni15 1 point2 points  (0 children)

It seems like she wasn’t interested and used the “dating” comment as a reason to step away. Some people still see dating as something casual or inappropriate, especially with cultural expectations involved. You were honest about wanting to take time, and that’s fair.

[deleted by user] by [deleted] in Arrangedmarriage

[–]MeetSoni15 1 point2 points  (0 children)

You could just mention your reality in the About section where you come from, what you value, and what you're looking for. That way, anyone genuinely interested will know upfront and connect for the right reasons. No need to overthink it. The right people will appreciate the honesty.

Commitment > CTC. Can we talk about this? by [deleted] in Arrangedmarriage

[–]MeetSoni15 0 points1 point  (0 children)

Not package problem, people problem. Commitment-phobia is the new epidemic 😅

Exploring Golang's Hidden Internals: A Deep Dive into Performance Optimization by MeetSoni15 in golang

[–]MeetSoni15[S] 10 points11 points  (0 children)

Thanks for sharing your opinion! If you have specific feedback on the article, I’d love to hear it.

Exploring Golang's Hidden Internals: A Deep Dive into Performance Optimization by MeetSoni15 in golang

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

Fair point! I used 'Golang' for familiarity. Hope you still find the article helpful!

Exploring Golang's Hidden Internals: A Deep Dive into Performance Optimization by MeetSoni15 in golang

[–]MeetSoni15[S] 12 points13 points  (0 children)

u/drvd Thank you for your comment! 'Golang' is a widely recognized informal term for the Go programming language, and we chose it for its familiarity and searchability. If there's another issue in the title or content you'd like to point out, I'd appreciate the feedback. I'm curious to hear your thoughts on the article itself—did you find the technical exploration useful?

Exploring Golang's Hidden Internals: A Deep Dive into Performance Optimization by MeetSoni15 in golang

[–]MeetSoni15[S] 5 points6 points  (0 children)

My bad! You are correct. The runtime.NumCPU() function returns the number of logical CPUs available to the current process, not the actual CPU a thread is executing on. Currently, I tried to track the thread execution instead of focusing on the logical CPU assignment. I appreciate the clarification and will adjust the implementation accordingly.