[DiscordArchive] <@160857905879449600> is it necessary for you to store all builds as strings? maybe we can do a sort
[DiscordArchive] <@160857905879449600> is it necessary for you to store all builds as strings? maybe we can do a sort
Original source
<@160857905879449600> is it necessary for you to store all builds as strings? maybe we can do a sort of range object in there?
rektbyfaith
11-05-2018, 08:22 AM #1Archived author: Skarn • Posted: 2018-11-05T08:22:21.205000+00:00
Original source
<@160857905879449600> is it necessary for you to store all builds as strings? maybe we can do a sort of range object in there?
Original source
that will implement the `__contains__` overloading similar to that C# code
rektbyfaith
11-05-2018, 08:22 AM #2Archived author: Skarn • Posted: 2018-11-05T08:22:42.627000+00:00
Original source
that will implement the `__contains__` overloading similar to that C# code
Original source
I have not measured memory usage but it wasn’t a problem for me. I obviously haven’t used that approach for the classic to wod range. This was the easiest way to do ranges and merging, it surely isn’t the best. It doesn’t work across minors anyway, so you can remove and change and refactor and redesign all you want, <@!197724887387734016>
rektbyfaith
11-05-2018, 08:35 AM #3Archived author: schlumpf • Posted: 2018-11-05T08:35:12.971000+00:00
Original source
I have not measured memory usage but it wasn’t a problem for me. I obviously haven’t used that approach for the classic to wod range. This was the easiest way to do ranges and merging, it surely isn’t the best. It doesn’t work across minors anyway, so you can remove and change and refactor and redesign all you want, <@!197724887387734016>
1 Guest(s)
1 Guest(s)