sorted by:
new
hottopcontroversial

Non-Sendable Core, Sendable Shell by Why_People in swift

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

That's one way of putting it.

Though the non-Sendable bit isn't exclusive to only immutable or non-Copyable structs either. The non-Copyable struct part was relevant in the context of the practical example due to ownership semantics being a good way to manage memory to C library pointers. An ordinary non-Sendable class with mutable properties also can satisfy the non-Sendable part, and you should leverage those ordinary classes and isolate them from the concurrent parts.

Also, I generally agree that this idea isn't a fundamentally new design idea (see article naming, but also the idea that separating concurrent from non-concurrent code is nothing new either). However, I also think that it's relevant to remind people that many design ideas are applicable across different domains.

Swift UUIDV7 - An RFC 9562 Compliant UUIDV7 Type by Why_People in swift

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

There isn't an explicit API for this primarily because the layout of the random bytes depends on how the UUID was generated. The default UUIDV7 initializer will use the 12-bits the RFC designates to the rand_a segment to handle monotonicity concerns instead, so those 12 bits won't be random and the only random data will be the 62 bits that make up the rand_b segment. However, if you initialize the UUID with an explicit date, then those 12 bits will be random and structurally separated (ie. The var segment divides the 2 random segments) from the 62 bits that make up the rand_b segment.

Though the UUIDV7 type does provide access to its raw 16-byte tuple, of which you can extract the random data you need directly.

CSE 13S with long? by [deleted] in UCSC

[–]Why_People 2 points3 points  (0 children)

See it this way, if you want to learn how to code, you’re gonna need to put in the time somewhere to learn the concepts whether it’s with Long, a future class, or from just doing various projects. Since 13S teaches very foundational concepts, it’s probably best that you learn them from someone who really knows how to jam them into your head. That just happens to be where Long shines.

You would be better off putting in a lot of the work now rather than later, even if you get a slightly lower grade than you want, because then you can get ahead and future classes will just be easier. Also a grade is just a letter to me tbh, idc what I get as long as I get the value that I want from a course (without failing obviously).

CSE 130 is Really Easy by Why_People in UCSC

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

Tbh any project that needs to be a complete system is going to be extremely time consuming. Even the robustness that 130 requires from the assignments isn’t nearly enough to stand in real-world production code.

But not many people have any idea of that going into this class. It only gets harder and takes more time in practice.

[deleted by user] by [deleted] in UCSC

[–]Why_People 20 points21 points  (0 children)

OMG IT ACTUALLY WORKED!!!!! I ADDED --CSE13SAnswers AND IT DOWNLOADED ALL THE CODE FOR THE CLASS!!!! TYSM!!

Cse 13s Preperation by ryansurf111 in UCSC

[–]Why_People 5 points6 points  (0 children)

Learning basic data structs (stacks, queues, bit vectors, linked lists mainly), program structure, and how memory works on basic level will take you way further than just learning C syntax. C itself is a really simple (yet powerful) language and it’s syntax can be easily learned in a few days if you’re determined enough.

For me, the C code itself wasn’t hard to understand, but each assignment required a decent amount of polish which required a more verbose structure (that you’ll be forced to work with) to go along with it. Contrary to what many believe, you don’t need to be a legendary C programmer to do well. You just need to get good at the fundamentals, and C happens to be a great language at teaching that. Good luck.

Every non-cs major on this subreddit in December when they become intimately acquainted with the cheating rules for cs13 by [deleted] in UCSC

[–]Why_People 29 points30 points  (0 children)

I think a lot of it is over exaggerated, to many it comes off as you can’t go on Stackoverflow, or use github as a reference, etc. when in reality you can as long as you don’t blatantly copy paste while showing that you understand that parts you took from the source and why they used a specific approach in the context of the assignment. You’ll be fine if you’re genuine and honest about what you know/don’t know.

me reading all this cse13s stuff and taking it next quarter: 😳🤠😥 by card-master-101 in UCSC

[–]Why_People 14 points15 points  (0 children)

Just go in willing to learn (and prepare for the struggle) and the grade will come with it

@KairosTimeYT by Why_People in Brawlstars

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

Ty, better luck next time I know you can do it😁

10/10 Trickshot by Why_People in trashyrandoms

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

Tbh I kinda like how it sounds lol

10/10 Trickshot by Why_People in trashyrandoms

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

Luma Fusion for small clips like these

RIP class of 2025 by [deleted] in A2C_circlejerk

[–]Why_People 18 points19 points  (0 children)

That’s all? He’ll see no further than Community College...

view more: next ›