clean up: remove redundant spaces

.travis.yml

@@ -7,15 +7,15 @@ matrix:
       addons:
         apt:
           sources:
-          - ubuntu-toolchain-r-test
+            - ubuntu-toolchain-r-test
           packages:
-          - gcc-5
-          - g++-5
-          - make
-          - libglfw3 
-          - libglfw3-dev
-          - libfreetype6-dev 
-          - libcurl3-dev
+            - gcc-5
+            - g++-5
+            - make
+            - libglfw3 
+            - libglfw3-dev
+            - libfreetype6-dev 
+            - libcurl3-dev
     - os: windows
       language: sh
       filter_secrets: false
@@ -24,8 +24,8 @@ matrix:
       addons:
         homebrew:
           packages:
-          - freetype
-          - glfw
+            - freetype
+            - glfw
       #env:
       #  - MATRIX_EVAL="brew install freetype glfw"
 script:
@@ -41,4 +41,3 @@ script:
   - export VROOT=$(pwd)
   - make
   - make test
-

CHANGELOG.md

@@ -1,7 +1,7 @@
 
-# 0.1.8 
+# 0.1.8
 - Single file programs without `fn main` now work as expected.
-- REPL has been fixed: it now supports imports, consts, function definitions, etc. 
+- REPL has been fixed: it now supports imports, consts, function definitions, etc.
 
 # 0.1.7
 

CodeStructure.md

@@ -32,8 +32,6 @@ It has only 8 files (soon to be 7):
 
 8. `json.v` defines the json code generation. This file will be removed once V supports comptime code generation, and it will be possible to do this using the language's tools.
 
-9. `x64/` is the directory with all the machine code generation logic. It will be available in early July. Obviously this is the most complex part of the compiler. It defines a set of functions that translate assembly instructions to machine code, it builds complicated binaries from scratch byte by byte. It manually builds all headers, segments, sections, symtable, relocations, etc. Right now it only has basic support of the x64 platform/Mach-O format, and it can only generate `.o` files, which then have to be linked with `lld`. 
+9. `x64/` is the directory with all the machine code generation logic. It will be available in early July. Obviously this is the most complex part of the compiler. It defines a set of functions that translate assembly instructions to machine code, it builds complicated binaries from scratch byte by byte. It manually builds all headers, segments, sections, symtable, relocations, etc. Right now it only has basic support of the x64 platform/Mach-O format, and it can only generate `.o` files, which then have to be linked with `lld`.
 
 The rest of the directories are vlib modules: `builtin/` (strings, arrays, maps), `time/`, `os/`, etc. Their documentation is pretty clear.
-
-

Makefile

@@ -3,18 +3,18 @@ all: clean v
 
 v: v.c
 	cc -std=gnu11 -w -o v v.c
-	./v -o v compiler 
-	rm v.c 
+	./v -o v compiler
+	rm v.c
 
 v.c:
 	curl -Os https://raw.githubusercontent.com/vlang/vc/master/v.c
 
 test: v
-	./v -prod -o vprod compiler # Test prod build 
-	echo "Running V tests..." 
+	./v -prod -o vprod compiler # Test prod build
+	echo "Running V tests..."
 	find . -name '*_test.v' -print0 | xargs -0 -n1 ./v
-	echo "Building V examples..." 
+	echo "Building V examples..."
 	find examples -name '*.v' -print0 | xargs -0 -n1 ./v
 
 clean:
-	-rm -f v.c v vprod 
+	-rm -f v.c v vprod