Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reflection.Emit cleanups #67170

Merged
merged 6 commits into from
Apr 19, 2022
Merged

Reflection.Emit cleanups #67170

merged 6 commits into from
Apr 19, 2022

Conversation

jkotas
Copy link
Member

@jkotas jkotas commented Mar 25, 2022

See commit descriptions for details

@ghost
Copy link

ghost commented Mar 25, 2022

Tagging subscribers to this area: @dotnet/area-system-reflection
See info in area-owners.md if you want to be subscribed.

Issue Details

See commit descriptions for details

Author: jkotas
Assignees: jkotas
Labels:

area-System.Reflection

Milestone: -

jkotas added 5 commits March 25, 2022 16:37
This check is trying to ensure that the Types passed in are somewhat well-behaving by verifying that
Module and Assembly properties are non-null. This validation is not done consistently and it has very
value. There are many other ways custom types can misbehave.

Also, this saves allocations of the object[] arrays for the params argument.
Simplify Exception.Source to avoid Reflection.Emit dependencies in Exception implementation
@vargaz
Copy link
Contributor

vargaz commented Mar 30, 2022

The mono changes look ok to me.

Copy link
Member

@steveharter steveharter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple feedback comments but otherwise LGTM.

@jkotas jkotas merged commit 3ab4120 into dotnet:main Apr 19, 2022
@jkotas jkotas deleted the ref-emit branch April 19, 2022 21:29
directhex pushed a commit to directhex/runtime that referenced this pull request Apr 21, 2022
* Delete AssemblyBuilder.CheckContext checks

This check is trying to ensure that the Types passed in are somewhat well-behaving by verifying that
Module and Assembly properties are non-null. This validation is not done consistently and it has very
value. There are many other ways custom types can misbehave.

Also, this saves allocations of the object[] arrays for the params argument.

* Simplify Exception.Source

Simplify Exception.Source to avoid Reflection.Emit dependencies in Exception implementation

* Delete unnecessary clone of CustomAttributeBuilder enumeration

* Factor out simple ModuleBuilder and TypeBuilder forwardering methods

* Delete ComVisible annotations in Mono

* Delete redundant FCall
@ghost ghost locked as resolved and limited conversation to collaborators May 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants