add reasons for not completing everything during GSOC

diff --git a/docs/gsoc-2017-landing-page.md b/docs/gsoc-2017-landing-page.md
index c63ff87a7578d738aa64419e630959f13b484d41..9d29cfb25cf3ec24da670061b8870449f71e0135 100644 (file)
--- a/docs/gsoc-2017-landing-page.md
+++ b/docs/gsoc-2017-landing-page.md
@@ -30,3 +30,7 @@ Not yet started:
 - Vulkan doesn't actually specify using the top-left fill rule. (I couldn't find it in the [rasterization section](https://www.khronos.org/registry/vulkan/specs/1.0-wsi_extensions/html/vkspec.html#primsrast-polygons-basic) of the Vulkan spec.)
 - SPIR-V is actually surprisingly complicated to parse for an IR that's supposed to be simple to parse. You have to determine the types of values before you can parse OpSwitch instructions properly as the number of words taken by each case depends on the bit-width of the value being switched on.
 - I probably should have used the SPIR-V parser that was already written by Khronos.
+
+## Why I didn't complete everything planned
+I think that I should have used the SPIR-V parser that was already written by Khronos, as I spent about a month writing the SPIR-V parser generator.
+I also think I over-engineering some of the utility code.