🚚 Add initial implementation

* 🎉 Setup strong_ptr repo

* 🚚 move strong ptr to it's own repo

* Delete .github/workflows/update_name.yml

* Delete ARCHITECTURE.md

* change requests

---------

Co-authored-by: Khalil Estell <kammcecorp@gmail.com>

Author: MaliaLabor

.clang-format

@@ -0,0 +1,10 @@
+BasedOnStyle: Mozilla
+Language: Cpp
+UseTab: Never
+AlwaysBreakAfterReturnType: None
+AlwaysBreakAfterDefinitionReturnType: None
+AllowShortFunctionsOnASingleLine: None
+FixNamespaceComments: true
+SpacesBeforeTrailingComments: 2
+ColumnLimit: 80
+QualifierAlignment: Right

.clangd

@@ -0,0 +1,3 @@
+CompileFlags:
+  CompilationDatabase: .
+  BuiltinHeaders: QueryDriver

.github/workflows/ci.yml

@@ -0,0 +1,33 @@
+# Copyright 2024 - 2025 Khalil Estell and the libhal contributors
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#      http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+name: ✅ CI
+
+on:
+  workflow_dispatch:
+  pull_request:
+  push:
+    branches:
+      - main
+  schedule:
+    - cron: "0 12 * * 0"
+
+jobs:
+  ci:
+    uses: libhal/ci/.github/workflows/library_check.yml@5.x.y
+    secrets: inherit
+
+  deploy_all_check:
+    uses: libhal/ci/.github/workflows/deploy_all.yml@5.x.y
+    secrets: inherit

.github/workflows/deploy.yml

@@ -0,0 +1,14 @@
+name: 🚀 Deploy
+
+on:
+  workflow_dispatch:
+  release:
+    types: [published]
+
+jobs:
+  deploy:
+    if: startsWith(github.ref, 'refs/tags/')
+    uses: libhal/ci/.github/workflows/deploy_all.yml@5.x.y
+    with:
+      version: ${{ github.ref_name }}
+    secrets: inherit

.github/workflows/take.yml

@@ -0,0 +1,30 @@
+# Copyright 2024 - 2025 Khalil Estell and the libhal contributors
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#      http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+# .github/workflows/take.yml
+name: 📛 assign issue to contributor
+on:
+  issue_comment:
+
+jobs:
+  assign:
+    name: Take an issue
+    runs-on: ubuntu-latest
+    steps:
+      - name: take the issue
+        uses: bdougie/take-action@main
+        env:
+          GITHUB_TOKEN: ${{ github.token }}
+        with:
+          message: Thanks for taking this issue! Let us know if you have any questions!

.gitignore

@@ -0,0 +1,60 @@
+# Prerequisites
+*.d
+
+# Compiled Object files
+*.slo
+*.lo
+*.o
+*.obj
+
+# Precompiled Headers
+*.gch
+*.pch
+
+# Compiled Dynamic libraries
+*.so
+*.dylib
+*.dll
+
+# Fortran module files
+*.mod
+*.smod
+
+# Compiled Static libraries
+*.lai
+*.la
+*.a
+*.lib
+
+# Executables
+*.exe
+*.out
+*.app
+
+# IDEs
+.vscode/
+archives/
+
+# GDB
+.gdb_history
+
+# Artifacts
+build/
+tools/
+
+# lint artifacts
+compile_commands.json
+.cache/
+
+# OS files
+.DS_Store
+
+# Conan Files
+graph_info.json
+conaninfo.txt
+conan.lock
+conanbuildinfo.txt
+
+# CMake
+CMakeUserPresets.json
+

CMakeLists.txt

@@ -0,0 +1,21 @@
+# Copyright 2024 - 2025 Khalil Estell and the libhal contributors
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+cmake_minimum_required(VERSION 3.15)
+
+project(strong_ptr LANGUAGES CXX)
+
+libhal_unit_test(SOURCES
+  tests/pointers.test.cpp
+  tests/main.test.cpp
+)

CODE_OF_CONDUCT.md

@@ -0,0 +1,85 @@
+# Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of
+experience, education, socio-economic status, nationality, personal appearance,
+race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening,
+offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+This Code of Conduct also applies outside the project spaces when the Project
+Steward has a reasonable belief that an individual's behavior may have a
+negative impact on the project or its community.
+
+## Conflict Resolution
+
+We do not believe that all conflict is bad; healthy debate and disagreement
+often yield positive results. However, it is never okay to be disrespectful or
+to engage in behavior that violates the project’s code of conduct.
+
+If you see someone violating the code of conduct, you are encouraged to address
+the behavior directly with those involved. Many issues can be resolved quickly
+and easily, and this gives people more control over the outcome of their
+dispute. If you are unable to resolve the matter for any reason, or if the
+behavior is threatening or harassing, report it. We are dedicated to providing
+an environment where participants feel welcome and safe.
+
+We will investigate every complaint, but you may not receive a direct response.
+We will use our discretion in determining when and how to follow up on reported
+incidents, which may range from not taking action to permanent expulsion from
+the project and project-sponsored spaces. We will notify the accused of the
+report and provide them an opportunity to discuss it before any action is taken.
+The identity of the reporter will be omitted from the details of the report
+supplied to the accused. In potentially harmful situations, such as ongoing
+harassment or threats to anyone's safety, we may take action without notice.
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 1.4,
+available at
+https://www.contributor-covenant.org/version/1/4/code-of-conduct/

CONTRIBUTING.md

@@ -0,0 +1,28 @@
+# How to Contribute
+
+We would love to accept your patches and contributions to this project.
+
+## Contribution process
+
+### :raised_hand: Self Assigning to an Issue
+
+If you find an issue you'd like to work on, simply type and submit a comment
+with the phrase `.take` in it to get assigned by our github actions.
+
+### :pencil2: Pull Request Guidelines
+
+1. Code must finish continuous integration steps before it will be reviewed.
+2. Commit messages should follow these guidelines here
+   https://cbea.ms/git-commit/.
+3. Pull requests should contain a single commit
+4. Pull requests should be small and implement a single feature where possible.
+   If it can be broken up into separate parts it most likely should be.
+5. Each PR should have an associated issue with it. Exceptions are made for very
+   small PRs such as fixing typos, fixing up documentation or removing
+   unnecessary headers.
+
+### Code Reviews
+
+All submissions, including submissions by project members, require review. We
+use [GitHub pull requests](https://docs.github.com/articles/about-pull-requests)
+for this purpose.

README.md

@@ -0,0 +1 @@
+# strong_ptr