pytorch / pytorch/gloo

uvw C++11 looks like a good idea

Open
#217 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
1.5k
Forks
368
Avg merge
19h 32m
Merged PRs (30d)
3

Description

I saw this commit and I must admit that it's an honor that Facebook has decided to use uvw.
Furthermore, I think that your idea of bringing it to C++11 may be of interest to many users. I was contacted by several people after switching to C++17, all of them asked to maintain a C++11/14 version, but I don't have enough bandwidth to do it myself right now since uvw is and has always been so far a free time project.

Do you think there is the possibility of a collaboration in this sense, given also your need?
Having Facebook as a partner would surely be an excuse but, more than anything else, knowing that you have someone who can support me with the development would give new life to the project and allow to support a C++11 version without problems.

I'm looking forward to your answer. Thank you in any case.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no Gloo files, tests, or entry points; it only references gloo/transport/uv/libuv.h and requests C++11/14 support. First clarify the intended compatibility scope and whether collaboration is available. Done would require an agreed implementation plan and verified support for the requested C++ versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.