Wrap operators unsupported in C# as named methods

Open
#631 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp, csharp
Domain
tooling

Research direction

No files, tests, or entry points are named. Audit how CppSharp currently handles each C++ operator that lacks a direct C# operator form, then determine the most appropriate named method or C# construct for each; the work is done when every such operator has an intentional representation or documented reason to remain ignored.

Written by the indexing model from the issue text.

Description

Many operators C++ has cannot be presented as operators in C#. We ignore at least some of such operators at present. However, they can and should be wrapped as named methods instead.
Note that some operators have more or less their equivalent in apparently unrelated C# constructs. For example, the assignment operator would best be represented by a C# copy constructor. If there already is one, the assignment operator can be safely ignored. So each operator should be inspected separately so that it can subsequently get its best possible C# representation.

Dominant language
C#
Stars
3.4k
Forks
541
No merged PRs in 30d

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.

More from mono/CppSharp

All issues in mono/CppSharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.