Anton
Anton
PostsComments
CC#
Created by Spielepapagei on 3/30/2025 in #help
Reflection error Object type T does not match target type System.RuntimeType.
you can, generics are available at runtime
11 replies
CC#
Created by Lukas on 3/31/2025 in #help
✅ Bubbel sorting
after each iteration, the largest element will be propagated through the whole array and end up last. then you kind of ignore the last position since it already has the largest element. repeat again, until there's nothing left to sort.
11 replies
CC#
Created by SWEETPONY on 3/31/2025 in #help
✅ How to convert controller route name to camel case automatically?
if you just want it for swagger, you need to dynamically parse routes, it's going to be a total mess, I don't recommend
19 replies
CC#
Created by SWEETPONY on 3/31/2025 in #help
✅ How to convert controller route name to camel case automatically?
or extend the framework, probably with a controller filter to be able to configure controller metadata
19 replies
CC#
Created by SWEETPONY on 3/31/2025 in #help
✅ How to convert controller route name to camel case automatically?
you have to type it like that manually for each class
19 replies
CC#
Created by SWEETPONY on 3/31/2025 in #help
✅ How to convert controller route name to camel case automatically?
not within that attribute
19 replies
CC#
Created by SWEETPONY on 3/31/2025 in #help
✅ How to convert controller route name to camel case automatically?
it's not possible like that
19 replies
CC#
Created by Filomeon on 3/28/2025 in #help
Default literal and non nullable reference types
you're welcome
90 replies
CC#
Created by Filomeon on 3/28/2025 in #help
Default literal and non nullable reference types
now that's the idea. I don't remember which way the stack grows though
90 replies
CC#
Created by Filomeon on 3/28/2025 in #help
Default literal and non nullable reference types
when you want to reference a, you'd do stack pointer (108) - fixed offset (8)
90 replies
CC#
Created by Filomeon on 3/28/2025 in #help
Default literal and non nullable reference types
to reach either one
90 replies
CC#
Created by Filomeon on 3/28/2025 in #help
Default literal and non nullable reference types
back
90 replies
CC#
Created by Filomeon on 3/28/2025 in #help
Default literal and non nullable reference types
so you offset from the address in the stack pointer, 108
90 replies
CC#
Created by Filomeon on 3/28/2025 in #help
Default literal and non nullable reference types
but you know they are in this order, a, then b
90 replies
CC#
Created by Filomeon on 3/28/2025 in #help
Default literal and non nullable reference types
when the function is called, the memory at 100 stores a value for a and the one at 104 stores a value for b, and the stack pointer gets bumped past those to 108
90 replies
CC#
Created by Filomeon on 3/28/2025 in #help
Default literal and non nullable reference types
stack pointer before the function call is at, say, 100
90 replies
CC#
Created by Filomeon on 3/28/2025 in #help
Default literal and non nullable reference types
like if a function has parameters named a and b
90 replies
CC#
Created by Filomeon on 3/28/2025 in #help
Default literal and non nullable reference types
Basically, every time you call a function, you allocate space (consecutive memory on the stack) for its parameters and locals (also called a stack frame), copy your values there, them bump the stack pointer to contain the address after that new memory. But the order in which you reserve this memory is consistent, so knowing either the start address of those locals or the address after you can reach any one of them. And functions do. They know that the stack pointer is going to have the address right after these locals, so they offset back from that address
90 replies
CC#
Created by Filomeon on 3/28/2025 in #help
Default literal and non nullable reference types
relative distance
90 replies
CC#
Created by Filomeon on 3/28/2025 in #help
Default literal and non nullable reference types
offset means distance from something
90 replies