Hacker Newsnew | past | comments | ask | show | jobs | submit | matthewwarren's commentslogin

Thanks for the link, looks interesting!


> Regardless, this doesn't actually sniff for ASCII art as much as comments themselves.

Yeah you're right. The regex just finds comments. I then wrote some very simple code that analysed the text inside the comments to find potentially interesting ASCII Art. I then looked through these manually to get the ones for the post.


> but in these cases it seems their purpose besides explanation is to imply that there is a good reason the code is the way it is, and that you had better have a very good reason to change the code (and the accompanying comment). In other words, they serve to also guard against change, in parts of the code which should not change often.

Interesting, I'd not thought about that 'side-effect', but you're right, it does guard against that


Wow, 'Stack Trace Art' is very cool, thanks for the links!


> Is there a detailed description of Test.CoreLib anywhere?

You can see the code and README for it here https://github.com/dotnet/corert/tree/master/src/Test.CoreLi... and I also wrote a bit about it in this post https://mattwarren.org/2018/06/07/CoreRT-.NET-Runtime-for-AO...


There's a high-res version on his blog https://lukecarvill.com/portfolio/london-transit-map/


Here's the talk abstract:

Have you ever stopped to think about all the things that happen when you execute a simple .NET program?

This talk will delve into the internals of the recently open-sourced .NET Core runtime, looking at what happens, when it happens and why.

Making use of freely available tools such as 'PerfView', we'll examine the Execution Engine, Type Loader, Just-in-Time (JIT) Compiler and the CLR Hosting API to see how all these components play a part in making 'Hello World' possible.


Here's the talk abstract:

Have you ever stopped to think about all the things that happen when you execute a simple .NET program?

This talk will delve into the internals of the recently open-sourced .NET Core runtime, looking at what happens, when it happens and why.

Making use of freely available tools such as 'PerfView', we'll examine the Execution Engine, Type Loader, Just-in-Time (JIT) Compiler and the CLR Hosting API to see how all these components play a part in making 'Hello World' possible.


Ah, I didn't realise that, thanks for the info


I don't know if it solves your specific scenario, but I do know that there's been some work done in this area.

See https://github.com/dotnet/source-build#net-core-build-script... and https://github.com/dotnet/arcade#arcade


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: