René Widera

@mehmetyusufoglu Please update the cheat sheet too! and check for other usages of `getValidWorkdiv(`

Maybe the problem is introduced in #2242 Before the change, we always declared the variable `extern` too see: https://github.com/alpaka-group/alpaka/pull/2242/files#diff-2eddedd7c8abe84214af714d0e61060a85e1ef924b16bad0e7bb6fff54b250b8L25 @AuroraPerego Do you know why you removed the additional `extern` declaration...

> > Do you know why you removed the additional `extern` declaration of the variable? > > With the new implementation the `extern` declaration was not working, I used the...

https://reviews.llvm.org/D88786?id=295997 looks like a discussion about this topic for llvm behaviours

fixed with https://github.com/alpaka-group/alpaka/pull/2303

> If not, would it be interesting to have it in Alpaka ? IMO this is interesting. A cool feature would be could handle such throws to avoid an application...

This approach is at least compatible too the current interface. This you could still be explicit with your ID. > How does it work when e.g. two header files, each...

I created ID's in a shared library within a function foo and in the main CPU. Linked it together and the IDs are unique. In general it should be because...

> Is it safer than the current approach? The user does not need to fiddle around with the counter makro and the interface will become nice because there is no...

Unfortunately, this solution is not working with nvcc within a GPU kernel. Cuda does not support lambda functions within an unevaluated context.