CI improvements

.github/workflows/build.yaml

@@ -24,3 +24,13 @@ jobs:
         uses: actions/setup-python@v3
         with:
           python-version: "3.9"
+
+      - name: Build
+        run: |
+          sudo apt update 
+          sudo apt install -y build-essential libffi-dev xz-utils powershell curl wget gnupg apt-transport-https
+          curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y
+          export PATH="/root/.cargo/bin:${PATH}"
+          export PATH="/root/.local/bin:$PATH"
+          cd src/munchkin
+          MK_DOWNLOAD_LLVM=true pwsh ./build.ps1

development.md

@@ -1,4 +1,4 @@
-### Rust++
+### R++
 
 Our Rust code is actually more like C++ due to some fun pointer manipulation we do and heavily interlinked data structures.
 
@@ -15,6 +15,6 @@ Except if you steal a reference, then it's on you to make sure the memory is not
 Otherwise you can just write Rust as normal, and anything not within a smart-pointer still has the usual rules.  
 
 Note: If you are concerned about this or are surprised it works at all - raw pointers have special designation, specially those in `UnsafeCell`'s.
-We are leaning upon some pretty niche documented constraints to keep within the bounds of Rusts expectations, if barely, but they are all official.
+We are leaning upon some pretty niche documented constraints to keep within the bounds of Rusts expectations, if barely.
 
-The language _almost_ works for what we need, so we bend it to meet that.
+We'll be keeping to this model until some of Rusts systems improve enough that we don't need oto.

src/munchkin/tests/qsharp/qaoa/QAOA.csproj

@@ -5,6 +5,7 @@
 	<QirGeneration>true</QirGeneration>
     <QscVerbosity>Detailed</QscVerbosity>
     <RuntimeIdentifier Condition="'$(RuntimeIdentifier)' == ''">$(NETCoreSdkRuntimeIdentifier)</RuntimeIdentifier>
+    <AssemblyName>qaoa</AssemblyName>
   </PropertyGroup>
 
   <ItemGroup>