Re: Five Projects Selected for SAOC 2019
On Wednesday, 4 September 2019 at 23:56:07 UTC, Laeeth Isharc wrote: On Tuesday, 27 August 2019 at 17:32:30 UTC, Max Haughton wrote: On Monday, 26 August 2019 at 18:51:54 UTC, Vladimir Panteleev wrote: [...] I was aware of the site when i wrote the proposal, but the idea is to create the infrastructure to add more measurements too, e.g. profiling the compiler or testing it under limited memory (I found out how much memory my CTFE thing was using the other day!). Assuming I can get it to work I'd also like to throw the Linux perf system in there too, Take a look at BPF. Might be some work to wrap and if I recall right some of the C headers are a bit gnarly. But it's pretty powerful. https://github.com/brendangregg/bpf-docs I'll look into it, thank you. Seems like a big rabbit hole to go down but the project is far from set in stone.
Re: Five Projects Selected for SAOC 2019
On Tuesday, 27 August 2019 at 17:32:30 UTC, Max Haughton wrote: On Monday, 26 August 2019 at 18:51:54 UTC, Vladimir Panteleev wrote: On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote: The Symmetry Autumn of Code 2019 application selection process has come to an end. This year, we've got five projects instead of three. Congratulations to everyone who was selected! You can read about them and their projects over at the D Blog: https://dlang.org/blog/2019/08/25/saoc-2019-projects-and-participants/ Sorry, I haven't been following. Don't we already have an implementation of the "Create a CI or other infrastructure for measuring D’s progress and performance" project? I just haven't been maintaining it because there hasn't been a lot of interest in it while it was being maintained. Here's the original blog post: https://blog.thecybershadow.net/2015/05/05/is-d-slim-yet/ I'll give it a kick and get it back online if there is interest. Seems wasteful to reimplement it from scratch, though. I was aware of the site when i wrote the proposal, but the idea is to create the infrastructure to add more measurements too, e.g. profiling the compiler or testing it under limited memory (I found out how much memory my CTFE thing was using the other day!). Assuming I can get it to work I'd also like to throw the Linux perf system in there too, Take a look at BPF. Might be some work to wrap and if I recall right some of the C headers are a bit gnarly. But it's pretty powerful. https://github.com/brendangregg/bpf-docs
Re: LDC 1.17.0
There's a new v1.17 Termux package for Android.
Re: Visual D 0.50.0 released
On Wednesday, 4 September 2019 at 18:27:14 UTC, Manu wrote: On Wed, Jun 26, 2019 at 1:30 AM a11e99z via Digitalmars-d-announce wrote: On Wednesday, 26 June 2019 at 02:35:53 UTC, Bart wrote: > On Tuesday, 25 June 2019 at 19:47:40 UTC, Rainer Schuetze Your problems are easy to resolve. BuildTools has some weird paths... but you're running VS; why are you using the separate build tools distribution when you have VS installed? This is thoroughly non-standard and weird. Just install the proper C++ tools? The path issue that lead to optlink rather than MS link should be trivial to resolve, then you will not have linking problems. yep, I fixed it already, its ok now - install internal build tools instead separate package. - reset VD settings (such issue was fixed by Schuetze). - fix PATH vars.
Re: Visual D 0.50.0 released
On Wed, Jun 26, 2019 at 1:30 AM a11e99z via Digitalmars-d-announce wrote: > > On Wednesday, 26 June 2019 at 02:35:53 UTC, Bart wrote: > > On Tuesday, 25 June 2019 at 19:47:40 UTC, Rainer Schuetze wrote: > > Before I told about problems with VD on my laptop. > Most of time I use desktop with VS2019 and VD0.49.2 - its working. > I dont have a few days for "debugging" my installation for now so > I put my laptop in case and I am afraid install new VD to > desktop. I will deeply plunge to this jungle at July. > I filled some issues/enhancement to bugtracker yesterday. > In any case thanks for VD, I like it and I need it. Your problems are easy to resolve. BuildTools has some weird paths... but you're running VS; why are you using the separate build tools distribution when you have VS installed? This is thoroughly non-standard and weird. Just install the proper C++ tools? The path issue that lead to optlink rather than MS link should be trivial to resolve, then you will not have linking problems.
Re: Five Projects Selected for SAOC 2019
On Monday, 26 August 2019 at 03:55:43 UTC, Andrej Mitrovic wrote: On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote: ... Solve Dependency Hell: This is considered as a crucial first step in making Phobos available via the DUB registry I'm guessing this means we might even be able to use multiple versions of Phobos one day. However before we do that, we will really need to fix the use of globals in Phobos. Honestly, I'm a bit leery about this use-multiple-versions approach. It feels like it carries some serious risks of code bloat, which may be accentuated by the fact that DUB has some serious dependency resolution bugs even with single version dependencies... :-\
Re: Going on holiday for the next 3 weeks...
On Wednesday, 4 September 2019 at 15:18:15 UTC, Atila Neves wrote: ... So not going to be available until I'm back. Have fun and relax! Happy holidays!
Going on holiday for the next 3 weeks...
... So not going to be available until I'm back.
Re: Visual D 0.50.0 released
On Tuesday, 3 September 2019 at 07:06:03 UTC, Rainer Schuetze wrote: I just released a bug fix version 0.50.1 with a few enhancements: - fixes some integration issues with VS 2019 16.2 - mago: improve function call in watch window - better version highlighting for files not in project Full list of changes as usual here: https://rainers.github.io/visuald/visuald/VersionHistory.html Thanks Rainer :)
