Print empty namespace or module.

[nojaf]

Fixes#13757

[nojaf]

@vzarytovskii@dsyme ready for review.

[0101]

What if there are multiple items in this list?

[nojaf]

That is a very unlikely scenario I believe.
You can only have this with two namespaces.
Fair enough, I've added a test.

[0101]

Should we also check for TMDefRec here? Consider these (and maybe add to tests):

modulerecFoobardo()

namespacerecFoobardo()

[nojaf]

modulerecFoobardo()

currently produces

moduleFoobarval``doval@3`` :unit

This probably isn't correct but is outside my scope here.

[0101]

There seems to be another edge case which could theoretically happen:

namespaceFoodo()namespaceBarmoduleBaz =do()

In this case it won't be matched and namespace Foo won't be in the signatures.

[nojaf]

I can live with that, the goal is to avoid purely empty file generation.
This will give a result because of the nested module and that is good enough for my use case.

[0101]

@nojaf we can have a separate issue to track the remaining inconsistencies if they're too difficult to fix right now. If you can add a docstring to (|EmptyModuleOrNamespaces|_|) then I think we can merge this.

[nojaf]

Thanks 👍, I see that I've added the docstring to the implementation file instead. I'll address that this afternoon.

[nojaf]

Fixes#13757

[nojaf]

@vzarytovskii@dsyme ready for review.

[0101]

What if there are multiple items in this list?

[nojaf]

That is a very unlikely scenario I believe.
You can only have this with two namespaces.
Fair enough, I've added a test.

[0101]

Should we also check for TMDefRec here? Consider these (and maybe add to tests):

modulerecFoobardo()

namespacerecFoobardo()

[nojaf]

modulerecFoobardo()

currently produces

moduleFoobarval``doval@3`` :unit

This probably isn't correct but is outside my scope here.

[0101]

There seems to be another edge case which could theoretically happen:

namespaceFoodo()namespaceBarmoduleBaz =do()

In this case it won't be matched and namespace Foo won't be in the signatures.

[nojaf]

I can live with that, the goal is to avoid purely empty file generation.
This will give a result because of the nested module and that is good enough for my use case.

[0101]

@nojaf we can have a separate issue to track the remaining inconsistencies if they're too difficult to fix right now. If you can add a docstring to (|EmptyModuleOrNamespaces|_|) then I think we can merge this.

[nojaf]

Thanks 👍, I see that I've added the docstring to the implementation file instead. I'll address that this afternoon.

[nojaf]

Fixes#13757

[nojaf]

@vzarytovskii@dsyme ready for review.

[0101]

What if there are multiple items in this list?

[nojaf]

That is a very unlikely scenario I believe.
You can only have this with two namespaces.
Fair enough, I've added a test.

[0101]

Should we also check for TMDefRec here? Consider these (and maybe add to tests):

modulerecFoobardo()

namespacerecFoobardo()

[nojaf]

modulerecFoobardo()

currently produces

moduleFoobarval``doval@3`` :unit

This probably isn't correct but is outside my scope here.

[0101]

There seems to be another edge case which could theoretically happen:

namespaceFoodo()namespaceBarmoduleBaz =do()

In this case it won't be matched and namespace Foo won't be in the signatures.

[nojaf]

I can live with that, the goal is to avoid purely empty file generation.
This will give a result because of the nested module and that is good enough for my use case.

[0101]

@nojaf we can have a separate issue to track the remaining inconsistencies if they're too difficult to fix right now. If you can add a docstring to (|EmptyModuleOrNamespaces|_|) then I think we can merge this.

[nojaf]

Thanks 👍, I see that I've added the docstring to the implementation file instead. I'll address that this afternoon.

[nojaf]

Fixes#13757

[nojaf]

@vzarytovskii@dsyme ready for review.

[0101]

What if there are multiple items in this list?

[nojaf]

That is a very unlikely scenario I believe.
You can only have this with two namespaces.
Fair enough, I've added a test.

[0101]

Should we also check for TMDefRec here? Consider these (and maybe add to tests):

modulerecFoobardo()

namespacerecFoobardo()

[nojaf]

modulerecFoobardo()

currently produces

moduleFoobarval``doval@3`` :unit

This probably isn't correct but is outside my scope here.

[0101]

There seems to be another edge case which could theoretically happen:

namespaceFoodo()namespaceBarmoduleBaz =do()

In this case it won't be matched and namespace Foo won't be in the signatures.

[nojaf]

I can live with that, the goal is to avoid purely empty file generation.
This will give a result because of the nested module and that is good enough for my use case.

[0101]

@nojaf we can have a separate issue to track the remaining inconsistencies if they're too difficult to fix right now. If you can add a docstring to (|EmptyModuleOrNamespaces|_|) then I think we can merge this.

[nojaf]

Thanks 👍, I see that I've added the docstring to the implementation file instead. I'll address that this afternoon.

[nojaf]

Fixes#13757

[nojaf]

@vzarytovskii@dsyme ready for review.

[0101]

What if there are multiple items in this list?

[nojaf]

That is a very unlikely scenario I believe.
You can only have this with two namespaces.
Fair enough, I've added a test.

[0101]

Should we also check for TMDefRec here? Consider these (and maybe add to tests):

modulerecFoobardo()

namespacerecFoobardo()

[nojaf]

modulerecFoobardo()

currently produces

moduleFoobarval``doval@3`` :unit

This probably isn't correct but is outside my scope here.

[0101]

There seems to be another edge case which could theoretically happen:

namespaceFoodo()namespaceBarmoduleBaz =do()

In this case it won't be matched and namespace Foo won't be in the signatures.

[nojaf]

I can live with that, the goal is to avoid purely empty file generation.
This will give a result because of the nested module and that is good enough for my use case.

[0101]

@nojaf we can have a separate issue to track the remaining inconsistencies if they're too difficult to fix right now. If you can add a docstring to (|EmptyModuleOrNamespaces|_|) then I think we can merge this.

[nojaf]

Thanks 👍, I see that I've added the docstring to the implementation file instead. I'll address that this afternoon.

[nojaf]

Fixes#13757

[nojaf]

@vzarytovskii@dsyme ready for review.

[0101]

What if there are multiple items in this list?

[nojaf]

That is a very unlikely scenario I believe.
You can only have this with two namespaces.
Fair enough, I've added a test.

[0101]

Should we also check for TMDefRec here? Consider these (and maybe add to tests):

modulerecFoobardo()

namespacerecFoobardo()

[nojaf]

modulerecFoobardo()

currently produces

moduleFoobarval``doval@3`` :unit

This probably isn't correct but is outside my scope here.

[0101]

There seems to be another edge case which could theoretically happen:

namespaceFoodo()namespaceBarmoduleBaz =do()

In this case it won't be matched and namespace Foo won't be in the signatures.

[nojaf]

I can live with that, the goal is to avoid purely empty file generation.
This will give a result because of the nested module and that is good enough for my use case.

[0101]

@nojaf we can have a separate issue to track the remaining inconsistencies if they're too difficult to fix right now. If you can add a docstring to (|EmptyModuleOrNamespaces|_|) then I think we can merge this.

[nojaf]

Thanks 👍, I see that I've added the docstring to the implementation file instead. I'll address that this afternoon.

[nojaf]

Fixes#13757

[nojaf]

@vzarytovskii@dsyme ready for review.

[0101]

What if there are multiple items in this list?

[nojaf]

That is a very unlikely scenario I believe.
You can only have this with two namespaces.
Fair enough, I've added a test.

[0101]

Should we also check for TMDefRec here? Consider these (and maybe add to tests):

modulerecFoobardo()

namespacerecFoobardo()

[nojaf]

modulerecFoobardo()

currently produces

moduleFoobarval``doval@3`` :unit

This probably isn't correct but is outside my scope here.

[0101]

There seems to be another edge case which could theoretically happen:

namespaceFoodo()namespaceBarmoduleBaz =do()

In this case it won't be matched and namespace Foo won't be in the signatures.

[nojaf]

I can live with that, the goal is to avoid purely empty file generation.
This will give a result because of the nested module and that is good enough for my use case.

[0101]

@nojaf we can have a separate issue to track the remaining inconsistencies if they're too difficult to fix right now. If you can add a docstring to (|EmptyModuleOrNamespaces|_|) then I think we can merge this.

[nojaf]

Thanks 👍, I see that I've added the docstring to the implementation file instead. I'll address that this afternoon.

[nojaf]

Fixes#13757

[nojaf]

@vzarytovskii@dsyme ready for review.

[0101]

What if there are multiple items in this list?

[nojaf]

That is a very unlikely scenario I believe.
You can only have this with two namespaces.
Fair enough, I've added a test.

[0101]

Should we also check for TMDefRec here? Consider these (and maybe add to tests):

modulerecFoobardo()

namespacerecFoobardo()

[nojaf]

modulerecFoobardo()

currently produces

moduleFoobarval``doval@3`` :unit

This probably isn't correct but is outside my scope here.

[0101]

There seems to be another edge case which could theoretically happen:

namespaceFoodo()namespaceBarmoduleBaz =do()

In this case it won't be matched and namespace Foo won't be in the signatures.

[nojaf]

I can live with that, the goal is to avoid purely empty file generation.
This will give a result because of the nested module and that is good enough for my use case.

[0101]

@nojaf we can have a separate issue to track the remaining inconsistencies if they're too difficult to fix right now. If you can add a docstring to (|EmptyModuleOrNamespaces|_|) then I think we can merge this.

[nojaf]

Thanks 👍, I see that I've added the docstring to the implementation file instead. I'll address that this afternoon.