Timeline for Handling related generic type parameters
Current License: CC BY-SA 4.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 24, 2018 at 19:27 | comment | added | NetMage | @Errorsatz Done. Ordering is so my example grouping won't create unnecessary groups. Imagine a 1D grouping rule: distance apart is less than 5. If you group 1,5,7 you get one group, if you group 1, 7, 5 you get two groups. | |
Sep 24, 2018 at 19:27 | history | edited | NetMage | CC BY-SA 4.0 |
added more sample code
|
Sep 24, 2018 at 17:58 | comment | added | NetMage |
@t3chb0t The original GroupBy groups according to a key calculated from a single item. This GroupBy groups according to a rule specified in each group, which could involve calculating across all previous group members. The example is about clustering points into groups that are "nearby" the centroid of the group.
|
|
Sep 22, 2018 at 11:01 | answer | added | user73941 | timeline score: 1 | |
Sep 22, 2018 at 8:45 | review | Close votes | |||
Sep 25, 2018 at 8:11 | |||||
Sep 22, 2018 at 8:26 | comment | added | t3chb0t |
And I'd like to ask you to explain what your GroupBy is actually doing? I cannot figure this out. How is it different from the original one?
|
|
Sep 22, 2018 at 0:47 | comment | added | Errorsatz | Could you post the code for gRectangleGroup? With your current design, it's not clear how BelongsToGroup could be implemented, given that all the groupings will be identical. It's also not clear what the purpose of ordering the items via IOrderable is. | |
Sep 22, 2018 at 0:04 | history | edited | NetMage | CC BY-SA 4.0 |
added 560 characters in body
|
Sep 21, 2018 at 23:48 | history | asked | NetMage | CC BY-SA 4.0 |