From f530e937c5b0ea1e06ff93fc6174fc73ebc57fcd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alexander=20K=C3=B6plinger?= Date: Tue, 3 Mar 2020 00:46:09 +0100 Subject: [PATCH] Fix typos in function pointers proposal (#3238) - Preventing -> Presenting - Fix markdown link --- proposals/function-pointers.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/proposals/function-pointers.md b/proposals/function-pointers.md index 5c1491f..4f6e873 100644 --- a/proposals/function-pointers.md +++ b/proposals/function-pointers.md @@ -13,8 +13,7 @@ potential implementation of the feature): https://github.com/dotnet/csharplang/issues/191 -This is an alternate design proposal to [compiler intrinsics] -(https://github.com/dotnet/csharplang/blob/master/proposals/intrinsics.md) +This is an alternate design proposal to [compiler intrinsics](https://github.com/dotnet/csharplang/blob/master/proposals/intrinsics.md) ## Detailed Design @@ -293,7 +292,7 @@ hide the fact that this is a pointer value and it kept peeking through even with the conversion to `object` can't be allowed, it can't be a member of a `class`, etc ... The C# design is to require `unsafe` for all pointer uses and hence this design follows that. -Developers will still be capable of preventing a _safe_ wrapper on top of `delegate*` values the same way that they do +Developers will still be capable of presenting a _safe_ wrapper on top of `delegate*` values the same way that they do for normal pointer types today. Consider: ``` csharp