Add helper to resolve namespace collision
See original GitHub issueMany projects use a module called datasets
, however this is incompatible with huggingface datasets. It would be great if there if there was some helper or similar function to resolve such a common conflict.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
How to properly use namespaces to avoid name collision?
I'm a bit confused concerning proper usage of C++ namespaces. It is clear for me how they can help to avoid conflicts (name...
Read more >Add helper API on RRef to call functions on remote objects
Add helper API on RRef to call functions on remote objects #31743 ... It also avoids the name collision and implicit RPC problems...
Read more >6.15 — Unnamed and inline namespaces - Learn C++
If you add a v3 namespace and want v3::doSomething() to be the resolved function when you call doSomething() unqualified, then you can just ......
Read more >Top 10 C++ header file mistakes and how to fix them
Mistake # 1: Not using “include guards” in a header file. · MISTAKE # 2: Incorporating "using namespace" statements at top level in...
Read more >User Procs and Helper Procs - 2022.1 English - Xilinx
When a user proc uses helper procs, it is recommended to create a sub-namespace under the app and move the user proc and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That’s a interesting option indeed. We’ll think about it.
Alternatively huggingface could consider some submodule type structure like:
import huggingface.datasets
import huggingface.transformers
datasets
is a very common module in ML and should be an end-user decision and not scope all of python ¯_(ツ)_/¯