Suggestion: rename Device.set_current() to Device.set_context()

[samaid]

Rationale:

• to be consistent with the method Device.create_context();
• to avoid ambiguity, e.g. device.set_current() tells nothing about what current is. Instead device.set_context() is self-explanatory.

[leofang]

Hey Sergey, sorry for late reply! As discussed in the past internal design meetings, we still have not decided if we want to expose CUDA contexts to Python. It will depend on the design investigations of e.g. #112 and #241. In particular, .set_current() is consistent with cudaSetDevice from CUDA Runtime, where it is the device being set to current, not the CUDA context (but see #548). Accepting a hypothetical context object is meant to be reserved as the entry point if the future design evolution requires it.