On Saturday, 19 July 2014 at 11:12:00 UTC, Marc Schütz wrote:
Casting to pure would break purity if the called function is
not actually pure. AFAIU, the problem is that the mutable
function pointers are not accessible from inside the pure
function at all, in which case the solution is to cast
On Friday, 18 July 2014 at 16:19:20 UTC, John Colvin wrote:
On Friday, 18 July 2014 at 16:12:18 UTC, Rene Zwanenburg wrote:
On Friday, 18 July 2014 at 15:57:40 UTC, John Colvin wrote:
On Friday, 18 July 2014 at 14:15:46 UTC, Rene Zwanenburg
wrote:
For all intents and purposes, the following
It's ok to deduce opDispatch as pure, but then its purity should
be enforced and error reported.
On 07/19/2014 03:53 PM, Kagamin wrote:
It's ok to deduce opDispatch as pure, but then its purity should be
enforced and error reported.
Why would it be ok to deduce opDispatch as pure only to report an error
that it is not actually pure? This would be a bug as well (albeit none
that causes
For all intents and purposes, the following code can be weakly
pure:
struct VAO
{
}
On Friday, 18 July 2014 at 14:15:46 UTC, Rene Zwanenburg wrote:
For all intents and purposes, the following code can be weakly
pure:
struct VAO
{
}
urrmm. Did you mean to post more than that?
On Friday, 18 July 2014 at 15:57:40 UTC, John Colvin wrote:
On Friday, 18 July 2014 at 14:15:46 UTC, Rene Zwanenburg wrote:
For all intents and purposes, the following code can be weakly
pure:
struct VAO
{
}
urrmm. Did you mean to post more than that?
Haha yup. Not sure what happened
