I noticed there isn't a mechanism to handle multiple events occurring on the same day, so only one event is chosen. There are two events scheduled on the same day, February 28th.
I noticed there isn't a mechanism to handle multiple events occurring on the same day, so only one event is chosen. There are two events scheduled on the same day, February 28th.
What mechanism do you think should be used to handle this issue, randomly selecting one from all the repeated events?
Maybe not randomly but generated from the hash function. (We might need to refactor the hash function first btw...)
> What mechanism do you think should be used to handle this issue, randomly selecting one from all the repeated events?
Maybe not randomly but generated from the hash function. (We might need to refactor the hash function first btw...)
OK.
That makes more sense. @ChenKaiLiuG and I, along with others, suggested not to refactor the hash function's calculation method or results, but only to refactor the way the function is written.
This hash function possesses a certain mystique, accurately predicting many things.
OK.
That makes more sense.
@ChenKaiLiuG and I, along with others, suggested not to refactor the hash function's calculation method or results, but only to refactor the way the function is written.
This hash function possesses a certain mystique, accurately predicting many things.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In this PR, we add some special events
These holidays and descriptions were proposed by me, @ChenKaiLiuG, and other classmates.
I noticed there isn't a mechanism to handle multiple events occurring on the same day, so only one event is chosen. There are two events scheduled on the same day, February 28th.
Ok.
I fixed
I mean there can be many events on the same day but we need a mechanism that can decide which event to go to instead of just following the order now.
What mechanism do you think should be used to handle this issue, randomly selecting one from all the repeated events?
Maybe not randomly but generated from the hash function. (We might need to refactor the hash function first btw...)
OK.
That makes more sense.
@ChenKaiLiuG and I, along with others, suggested not to refactor the hash function's calculation method or results, but only to refactor the way the function is written.
This hash function possesses a certain mystique, accurately predicting many things.
I think this function can be refactored and separated to make it reusable.
Indeed, just like in this kind of scenario.
I will rebase it.
@LifeAdventurer Rebase fininshed
@@ -20,6 +20,46 @@"r_2_desc": ""Shorten this description.
Keep this event and description blank.
@@ -40,6 +80,166 @@"r_2_desc": ""Shorten this description.
Shorten this description.
Shorten this description.
Keep this event and description blank.
Shorten this description.
Shorten this description.
Shorten this description.