Not sure who to contact about https://run.dlang.io/ or anything so here goes.

Is it possible to have caching an optional thing?

When you're running snippets that has anything to do with time then you need to change the code every time to get proper results and it's tedious.

I thought there was a bug in my code, but it was just because the output was cached.

On Friday, 26 July 2019 at 09:51:04 UTC, bauss wrote:
> Not sure who to contact about https://run.dlang.io/ or anything so here goes.

https://github.com/dlang-tour/core/issues


> Is it possible to have caching an optional thing?

Not really, sorry. The caching is required which makes it a lot tractable to send serve many requests.

> When you're running snippets that has anything to do with time then you need to change the code every time to get proper results and it's tedious.

The proper solution would be to set the time to a fixed date then, s.t. people don't get confused.

On Friday, 26 July 2019 at 14:23:47 UTC, Seb wrote:
> On Friday, 26 July 2019 at 09:51:04 UTC, bauss wrote:
>> Not sure who to contact about https://run.dlang.io/ or anything so here goes.
>
> https://github.com/dlang-tour/core/issues
>
>
>> Is it possible to have caching an optional thing?
>
> Not really, sorry. The caching is required which makes it a lot tractable to send serve many requests.
>
>> When you're running snippets that has anything to do with time then you need to change the code every time to get proper results and it's tedious.
>
> The proper solution would be to set the time to a fixed date then, s.t. people don't get confused.

Well my snippet was about generating some timestamps and then generating some results based on that and with a fixed time it would look like all results were generated the same.

Ex. it was actually a small snippet for a random generator.

So I was really confused by it and thought there was a bug in my code since 1. the seed would always be the same 2. all numbers generated were the same because of that.