My personal website source code
Log | Files | Refs | Submodules | README | LICENSE

commit ddd937c61c07c78a3b3272314a0f19be7ee4d059
parent 6a7d848590acb493dd62f9d8fd2660827c9d36cd
Author: Luís Ferreira <[email protected]>
Date:   Thu, 28 Oct 2021 17:33:15 +0100

content: use IPFS static content instead of non-IPFS content

Signed-off-by: Luís Ferreira <[email protected]>

Mcontent/posts/ | 2+-
Mcontent/posts/ | 2+-
Mcontent/posts/ | 2+-
3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/posts/ b/content/posts/ @@ -22,7 +22,7 @@ challenge. Why you may ask? Because looking at the [ABI specification]( a lot of mangling nodes are dependent of each other and splitting 3000 lines of code into small, stackable and independent patches needs some planning. I tried several layouts and -[this]( one seems +[this](../../public/assets/posts/d-saoc-2021-03/ one seems to work out the best, so I'm sticking with it. Unfortunately, this week was kinda unproductive as I mostly spent this week diff --git a/content/posts/ b/content/posts/ @@ -45,7 +45,7 @@ only C VLAs are using it. I wrote a document describing some of the issues and comparing the DWARF capabilities of the 3 most known D compilers. You can read it -[here]( +[here](../../public/assets/posts/d-saoc-2021-05/ Some of those issues I managed to fix in the compiler backend, others I filed a bug. Here is a list of patches and bug reports I created: diff --git a/content/posts/ b/content/posts/ @@ -87,7 +87,7 @@ ldc2 -g app.d ``` You can also use -[this]( file, +[this](../../public/assets/posts/d-saoc-2021-06/app.d) file, which is what I use to test the D plugin and used to show the above example. ### Issues