[DiscordArchive] <@200677690838220800> you don't like std::function due to concerns about performance or abstraction
[DiscordArchive] <@200677690838220800> you don't like std::function due to concerns about performance or abstraction
Original source
nutjobs surely take care not to hit those
rektbyfaith
07-07-2025, 08:37 PM #11Archived author: Warpten • Posted: 2025-07-07T20:37:17.391000+00:00
Original source
nutjobs surely take care not to hit those
Original source
i can move relevant functions into Spell class as some spell helper module and add some type of shuffling for equal-priority entries if you don't like the deterministic change I suggested
rektbyfaith
07-07-2025, 08:38 PM #12Archived author: Telegrill • Posted: 2025-07-07T20:38:16.795000+00:00
Original source
i can move relevant functions into Spell class as some spell helper module and add some type of shuffling for equal-priority entries if you don't like the deterministic change I suggested
Original source
or so I think, the idea was being able to create dynamic rules of prioritization as you see fit, every spell works differently but still using a base system for it
rektbyfaith
07-07-2025, 08:44 PM #13Archived author: Telegrill • Posted: 2025-07-07T20:44:44.539000+00:00
Original source
or so I think, the idea was being able to create dynamic rules of prioritization as you see fit, every spell works differently but still using a base system for it
Original source
i just don't think I can find a suitable change without using std::function because the idea relies on creating dynamic lambdas per script because it adds flexibility to evolving logic huh
rektbyfaith
07-07-2025, 08:49 PM #14Archived author: Telegrill • Posted: 2025-07-07T20:49:44.793000+00:00
Original source
i just don't think I can find a suitable change without using std::function because the idea relies on creating dynamic lambdas per script because it adds flexibility to evolving logic huh
Original source
the only "solution" I can think of would be creating a virtual interface to create struct conditions, but that is more boilerplate and less concise because it requires a struct per condition which are global and most likely unusable by other scripts than using plain lambdas which offers flexibility
rektbyfaith
07-07-2025, 08:56 PM #15Archived author: Telegrill • Posted: 2025-07-07T20:56:31.873000+00:00
Original source
the only "solution" I can think of would be creating a virtual interface to create struct conditions, but that is more boilerplate and less concise because it requires a struct per condition which are global and most likely unusable by other scripts than using plain lambdas which offers flexibility
Original source
you know, another option would be to just leave the default injured selector intact, without migrating it to also use the std::function based one
rektbyfaith
07-07-2025, 09:10 PM #16Archived author: Tea • Posted: 2025-07-07T21:10:39.597000+00:00
Original source
you know, another option would be to just leave the default injured selector intact, without migrating it to also use the std::function based one
1 Guest(s)
1 Guest(s)