Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Enable marshal methods support by default #7351
Enable marshal methods support by default #7351
Changes from 136 commits
35f4e24
e34f88e
eb15bd2
a80e4a1
49751f7
803b3e3
e6101c1
657aff0
e8d3026
4d7ec30
39068d3
82ece43
acd5bc8
9a476d8
8d2503f
f913d24
52c99db
e5358f4
2f15f67
21c066f
3c8901a
7dc40fc
2b2ce55
9c38c68
85f2cfa
024b5f5
4d92570
20a2f00
2d3c043
071e9d3
710242e
af91895
673836c
ca2f92d
10e63e2
238417e
72c4b60
eb94adc
a8471cd
cfaabf2
8ca61bb
a473f27
d99b7e3
cfa1b30
9c9612d
334619b
c9332a8
e518a4e
905e784
f29f0d2
6ca1245
b988b7f
63bf193
3530c39
c516792
c8a2d9f
e8f3215
b60c767
0aa3e95
e3ac595
49895b8
a8cfd90
92fa671
f37b4dc
09678bd
d60fc08
6b116bf
1d88be2
aea0b0f
e1e59f0
aaff9f5
df04d47
7e9761f
f17ad9f
7a00e0e
d3d9007
73237a2
b459e4a
dfcf734
5dccadb
fc83958
8bdb607
cd832c7
a9995b0
86d9fca
1162a09
65471a8
7f87a37
ea4c57f
115c6fa
222163e
5bd03e2
e635b27
221ad8f
d03092d
e1a621e
f9bca3c
977a060
09eeb7e
312d84e
b143c95
c20ae31
8c9ceca
2b33563
94d9bea
73277aa
5b14a70
9077b6a
32347b7
ddedcc3
aed7b2d
2aa7cfe
92fb339
d3c54a0
170b5d1
3fdc653
504ced9
be9280e
983ad70
7d201e3
35d49d4
1ebb5d8
62a5138
9852cc5
fe2ae06
e1609d9
98655ea
5d138d0
71aafd5
d708edc
7124851
9be7e6b
edcf092
48c3328
5781643
5f433b1
8b1d3f9
724de1d
d26d9e1
d5016fe
f8db2d2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fear that I'm gonna be "bikeshedding" half the naming here -- and I am! -- but…
Mono.Android.Runtime
is not "future-facing". We may stick withMono.Android.dll
"forever", but there are equal odds that we may do aMicrosoft.Android.dll
name in the future (.NET 10?).As such, we should choose names which are unlikely to need changing. Possible suggestions:
Microsoft.Android.Startup.dll
Microsoft.Android.Internals.dll
Microsoft.Android.Interop.dll
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd rather keep it
Mono.Android.Runtime
for now, since it pairs nicely withMono.Android
(and that was the reason I chose this name)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I forget; does
JNIEnvInit
need to remain inMono.Android.dll
? Or can it be moved to the assembly containingAndroidRuntimeInternal
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It remains there for classic Xamarin, it is moved to the new assembly for .NET
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…and more name bikeshedding: I think it was a historical mistake to use
Android.Runtime
; we're lucky that Google never introduced anandroid.runtime
package.I think
Microsoft.Android.Internals
would be a good namespace, or justMicrosoft.Android
, as all the types here areinternal
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Likewise, I'd rather keep the
Android.Runtime
namespace, because this assembly includes sources fromMono.Android
that are in this namespace. If we want to rename it, we should rename it all at once one day.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if this should
abort
; if we hit here, either we're very early in startup -- which means aborts would be bad ;-) -- or something is Very Wrong™.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't abort explicitly here. Hitting it during startup is very unlikely, and if it's not properly initialized, the app will crash anyway, implicitly aborting.