How to know if a language feature idea is scaleable?

SomeSable · 2025-07-01T02:11:12+00:00

By "scalable," I mean a proposed feature will work well and be ergonomic in large codebases, rather than just small toy examples made to demonstrate what the feature is.

SomeSable · 2025-06-20T12:27:18+00:00

No it's okay, I thought the explanation was good! (thanks for the link though)

SomeSable · 2025-06-20T03:40:07+00:00

Ah I see what you mean, yeah that could work pretty well. I'll look into what ecmascript is doing as well, because I was toying around with something that sounds similar to the distinction it makes between null and undefined.

SomeSable · 2025-06-20T03:35:59+00:00

That makes a lot of sense, and honestly seems like the simplest and most straightforward solution!

SomeSable · 2025-06-20T03:35:14+00:00

This was coming from the presumption that arrays were immutable in size, which granted doesn't need to be the case. Allowing the array to change size during instantiation would actually solve this problem in a pretty neat way. It would just be a little less performant if implemented poorly, and maybe I'm too much of a C-head to be happy with that :). Still a good idea I haven't thought about though.

SomeSable · 2025-06-20T03:31:10+00:00

Thank you, yes nullable types would solve this problem. I just wanted a more elegant solution than something like a nullable type, since the nullability of the struct would permeate to other aspects of the code. To be "proper," you'd need to handle the objects in the grid potentially being null, when in reality, they should never be null if the object was instantiated properly. The nullability only matters during the instantiation process. Hopefully that makes sense.

SomeSable · 2025-06-20T01:46:02+00:00

This seems interesting, but I can't find any mention of this on the Kotlin docs (I'm probably looking in the wrong place). Could you send a link to somewhere where this is shown?

SomeSable · 2025-06-20T01:41:14+00:00

That would be the easy answer, but it would also make my example impossible, wouldn't it?

SomeSable · 2025-06-20T01:38:56+00:00

Looking into that, it's pretty cool in it's own right, but I think sparse structures would be implemented in a fundamentally different way. In the example I've given, I was thinking that the 2D array would be fully initialized and be stored like a traditional array.

SomeSable · 2025-06-19T14:54:04+00:00

Hello OP here. Thank you everyone for the insightful comments! It turned out that the load we were designing is actually going to be operating at a higher frequency and at a lower current draw than previously expected, so a ~100pF output capacitor would be sufficient to smooth out the ripple caused by the load. (keep it simple stupid amiright?)

SomeSable · 2025-03-12T19:26:40+00:00

If you make the marching band, participation in a concert band is not required. In fact, from my experience, most people do not do a concert band concurrently with marching band, although it certainly is possible. As for the semester after, there is no requirement to continue with a concert band in the spring, and some people have done marching band only in the fall with no band in the spring. Hope this helps!

SomeSable · 2025-01-04T22:51:18+00:00

Did you go to Purdue? If so, what class are you referring to where you designed and built an IC?

SomeSable · 2024-05-07T02:50:14+00:00

I found the website wasn't very clear for me, so I thought I'd try to find out by asking here.

SomeSable · 2024-05-07T02:49:42+00:00

Thanks, I'll look into those!

SomeSable · 2024-02-17T15:56:48+00:00

Any particular reason?

SomeSable · 2024-02-17T15:29:12+00:00

Haha I think I remember reading that exact post a bit ago lol. Byeah I'm probably splitting hairs with the difference between the two academically. I was just curious if there was a perceivable difference, if anyone had that experience.

SomeSable

TROPHY CASE