Ignored private field still exported

Open
#748 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, csharp
Domain
tooling

Research direction

The issue names no source file or test. Reproduce the shown AttributeConfig declaration, trace the C++-to-C# field emission path, and verify that CS_IGNORE prevents _attribs from appearing while other fields remain exported.

Written by the indexing model from the issue text.

Description

C++ code:

class CS_API AttributeConfig
{
	CS_IGNORE std::vector<kit::Matching::AttributeMetadata> _attribs;
public:
	AttributeConfig() {}
        // etc.
};

C# code includes the _attribs field which was previously (and needs to be) skipped.

public unsafe partial class AttributeConfig : IDisposable
            {
                [StructLayout(LayoutKind.Explicit, Size = 32)]
                public partial struct __Internal
                {
                    [FieldOffset(0)]
                    internal global::Std.Vector.__Internal _attribs;
                    // etc.

Note that the _attribs is not actually used anywhere else in C#; it could totally not be there and everyone would be happy. It is there on the C++ type and needs to be, but it is private and marked CS_IGNORE which in previous versions meant it would not be emitted.

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.