Edit this page

SemPtr

SemPtr (short for Semantic Pointers) is a semantic pointer library for .NET that aims to overcome the limitations of traditional pointers (i.e., raw pointers) in C#.

This documentation provides you with articles and an API documentation to help you understand what SemPtr is about and how to use it effectively.

Note

This documentation is work-in-progress.

For a while, AI was used to help in the creation of this documentation to speed up its completion. But the required effort to make sure the quality and accuracy of the content is maintained is out of proportion compared to the benefits it provides.
That's why, going forward, the majority of the remaining documentation will be primarily written and verified by humans. And as long as this process is not completed, the documentation will remain in a work-in-progress state.
Sadly, this could mean that completing the documentation might take a bit more time.

(There might be a drop in the quality of the English language used in some parts of the documentation due to the sole author being a non-native speaker.)

If you want to know more about the usage of AI in this documentation, see A Note on AI Usage.

Further Resources

If you're looking for other resources about SemPtr, you can refer to the following:

  • GitHub Repository: GitHub
  • GitHub Releases: GitHub Release
  • NuGet Package Release: NuGet

A Note on AI Usage

This is a disclaimer and I want to be honest and upfront about the usage of AI in this documentation.

This documentation has been partially generated with the help of AI.

While all the informations on here, regardless of whether they were generated by AI or written by humans, should have been carefully verified and approved, there's still a possibility of errors or inaccuracies due to human mistakes. So please treat the content with caution.

If you want to know more about the usage of AI in this documentation, see Why AI?.

Because of the limitations of AI technology, there was made a recent decision to use less AI in the creation of this documentation moving forward. The reason for that is the enormous effort required to make sure that the AI has a well enough understanding of the codebase and its public API semantics, which is hard to achieve consistently for the complex low-level nature of the project.