removing visual studio installer and changing cache

.github/workflows/ci.yml

@@ -24,7 +24,7 @@ jobs:
           if ($LASTEXITCODE) { throw "Error" }
           ./target/release/ty obj test/main.ty
           if ($LASTEXITCODE) { throw "Error" }
-          ./target/release/ty link main -o .ty-cache/main.o
+          ./target/release/ty link main -o .ty/main.o
           if ($LASTEXITCODE) { throw "Error" }
           ./target/main
           if ($LASTEXITCODE) { throw "Error" }
@@ -42,7 +42,7 @@ jobs:
           cargo test
           ./target/release/e2e
           ./target/release/ty obj test/main.ty
-          ./target/release/ty link main -o .ty-cache/main.o
+          ./target/release/ty link main -o .ty/main.o
           ./target/main
 
   build-macos:
@@ -57,5 +57,5 @@ jobs:
           cargo test
           ./target/release/e2e
           ./target/release/ty obj test/main.ty
-          ./target/release/ty link main -o .ty-cache/main.o
+          ./target/release/ty link main -o .ty/main.o
           ./target/main

.gitignore

@@ -2,7 +2,7 @@
 callgrind*
 
 # type lang
-.ty-cache
+.ty
 #windows installer
 .vs
 # Generated by Cargo
@@ -18,4 +18,4 @@ Cargo.lock
 
 # Added by cargo
 
-/target
+target

README.md

@@ -1,8 +1,9 @@
 # type-lang
 
-Type-lang or __ty__. Is a rust/zig/typescript inspired language. There is one main goal of __ty__ and that is to become the best high level language without a Garbage Collector. Every decision for syntax, language features, and implementation will point back to that main goal.
+Type-lang or **ty**. Is a rust/zig/typescript inspired language. There is one main goal of **ty** and that is to become the best high level language without a Garbage Collector. Every decision for syntax, language features, and implementation will point back to that main goal.
 
 #### Build from source
+
 Ty requires a relatively recent version of cargo.
 
 ```
@@ -32,17 +33,16 @@ You can view the location of the current main test file here.
 [main.ty](./test/main.ty)
 That file will have almost every feature once it is supported, so check the file, for possibilities
 
-
 Future versions of ty will have a much more robust easy to use build system.
 For now, compiling a program requires these steps, first generate the object files
 
 `ty obj main.ty,other.ty`
 
-this puts the object files in a directory `.ty-cache`
+this puts the object files in a directory `.ty`
 
 then link to a final executable.
 
-`ty link my-cli -o .ty-cache/main.o,.ty-cache/other.o`
+`ty link my-cli -o .ty/main.o,.ty/other.o`
 
 you can then execute your new binary.
 

e2e/src/main.rs

@@ -19,10 +19,10 @@ fn main() {
         }",
         Path::new("main.ty"),
     );
-    let input = Path::new(".ty-cache/main.o").to_path_buf();
-    let output = Path::new(".ty-cache/main").to_path_buf();
+    let input = Path::new(".ty/main.o").to_path_buf();
+    let output = Path::new(".ty/main").to_path_buf();
     link(vec![&input], &output);
-    let output = Command::new(".ty-cache/main")
+    let output = Command::new(".ty/main")
         .args(&[""])
         .spawn()
         .expect("main to run")

installers/windows/.gitignore

@@ -1,2 +1 @@
-Release
-Debug
+Output