Re: DConf 2018 Livestream

[meppl via Digitalmars-d-announce]

On Friday, 4 May 2018 at 06:19:13 UTC, meppl wrote:

On Friday, 4 May 2018 at 04:39:16 UTC, Nemanja Boric wrote:
On Friday, 4 May 2018 at 00:09:53 UTC, Nick Sabalausky 
(Abscissa) wrote:

On 05/03/2018 11:12 AM, Nemanja Boric wrote:

[...]


It's working for me:
https://www.youtube.com/watch?v=0UZuRNujLGQ

Maybe youtube just needed some time after the original stream 
ended before it could do replays of the whole thing.


Looks like it, it works for me now as well!

This looks like to be the first day (or recorded part of it): 
https://www.youtube.com/watch?v=HvqsUO77FGI


The second day (from your post): 
https://www.youtube.com/watch?v=0UZuRNujLGQ




no, its the other way around. also, "walter bright"-talk and 
some other are still missing


ah, sorry, i was confused. the order is right. but some 
presentations are really missing/lost

Re: DConf 2018 Livestream

[meppl via Digitalmars-d-announce]

On Friday, 4 May 2018 at 04:39:16 UTC, Nemanja Boric wrote:
On Friday, 4 May 2018 at 00:09:53 UTC, Nick Sabalausky 
(Abscissa) wrote:

On 05/03/2018 11:12 AM, Nemanja Boric wrote:

On Thursday, 3 May 2018 at 12:24:16 UTC, Per Nordlöw wrote:

[...]


It looks like you can just watch inside last two hours window.


It's working for me:
https://www.youtube.com/watch?v=0UZuRNujLGQ

Maybe youtube just needed some time after the original stream 
ended before it could do replays of the whole thing.


Looks like it, it works for me now as well!

This looks like to be the first day (or recorded part of it): 
https://www.youtube.com/watch?v=HvqsUO77FGI


The second day (from your post): 
https://www.youtube.com/watch?v=0UZuRNujLGQ




no, its the other way around. also, "walter bright"-talk and some 
other are still missing

Re: LDC 1.9.0 beta

[meppl via Digitalmars-d-announce]

On Tuesday, 24 April 2018 at 15:53:23 UTC, Joakim wrote:

On Monday, 23 April 2018 at 09:18:07 UTC, Suliman wrote:
What about Webassembly support? Latest LLVM suppport it, so 
LDC should support also.


We don't support a lot of platforms that llvm supports. It will 
require someone to work on the port, which hasn't happened. 
I've said before that I don't think it's worth it, because the 
web has been declining as a platform:


https://forum.dlang.org/post/unqvdzopebfksnxwh...@forum.dlang.org



I stumbled over this:
http://blog.qt.io/blog/2018/04/23/beta-qt-webassembly-technology-preview/
https://sdtimes.com/webdev/mozillas-webassembly-studio-enters-beta/

I dont want to argue, just throwing that in ;)

Re: Beta 2.079.0

[meppl via Digitalmars-d-announce]

On Saturday, 31 March 2018 at 00:25:47 UTC, Seb wrote:
On Tuesday, 20 February 2018 at 08:43:50 UTC, Martin Nowak 
wrote:

On Monday, 19 February 2018 at 15:58:57 UTC, Joakim wrote:

[...]


No need to use it if you don't like it. It's particularly 
useful for small examples, localized imports and hacking.
It's mainly a generalisation of the existing possibility to 
mix module imports and one selective import at the end.
If you prefer java-like 50 lines import manifests, then by all 
means keep using those.

How would that feature cause bugs though?


AFAICT Rust now has introduced the exactly same feature. It's 
quite interesting to see that there was no outcry by the 
community and it was universally liked:


https://blog.rust-lang.org/2018/03/29/Rust-1.25.html
https://github.com/rust-lang/rust/issues/44494


the curly brackets make the rust implementation more readable. 
The dmd implementation didn't use brackets. I believe that's a 
main reason for the resistance from the people

Re: D_vs_nim: git repo to compare features of D vs nim and help migrating code bw them. PRs welcome

[meppl via Digitalmars-d-announce]

On Tuesday, 27 March 2018 at 04:46:21 UTC, meppl wrote:

On Tuesday, 27 March 2018 at 01:25:42 UTC, timotheecour wrote:

...


Sometimes I want to use a debugger like gdc. If it works, it 
can be really useful. I skipped trying out Nim, because 
debugging was not really supported. I wonder, if this is fixed 
now


I wanted to write "gdb" of course.
There is an article about debugging nim:
https://nim-lang.org/blog/2017/10/02/documenting-profiling-and-debugging-nim-code.html#using-gdb-lldb

Re: D_vs_nim: git repo to compare features of D vs nim and help migrating code bw them. PRs welcome

[meppl via Digitalmars-d-announce]

On Tuesday, 27 March 2018 at 01:25:42 UTC, timotheecour wrote:

D and nim are both very promising.
I created this git repo to compare them:

https://github.com/timotheecour/D_vs_nim/

Goal: up to date and objective comparison of features between D 
and nim (to help deciding what language to use), and 1:1 map of 
features and libraries to help D users learn nim and vice versa.


PRs are welcome and merged fast


Sometimes I want to use a debugger like gdc. If it works, it can 
be really useful. I skipped trying out Nim, because debugging was 
not really supported. I wonder, if this is fixed now

Re: State of D 2018 Survey

[meppl via Digitalmars-d-announce]

On Wednesday, 28 February 2018 at 13:41:56 UTC, Mike Parker wrote:


https://seb134.typeform.com/to/H1GTak



I might have overseen it, but in the survey I missed the feature 
"being able to allocate withing @nogc-CTFE-functions". Some 
people want to promote a @nogc library and they cant use CTFE to 
the full extend then.

( see also: https://issues.dlang.org/show_bug.cgi?id=18119 )

Re: Beta 2.079.0

[meppl via Digitalmars-d-announce]

On Monday, 19 February 2018 at 23:37:49 UTC, Mike Franklin wrote:

On Monday, 19 February 2018 at 18:50:47 UTC, Dukc wrote:

...



Mike



@"16.": https://dlang.org/changelog/2.079.0.html#minimal_runtime

So, now someone could "easily" write his own memory managment for 
allocations who would be usually done by the default GC - e.g. 
classes?

Re: The ShionKeys project has quietly raised money on indiegogo

[meppl via Digitalmars-d-announce]

On Tuesday, 16 January 2018 at 19:15:52 UTC, artishu wrote:

On Monday, 15 January 2018 at 06:54:04 UTC, ShionKeys wrote:

ShionKeys: I want to change the world
World: You will be alone
... ...
https://igg.me/at/ShionKeys/x/17399884
https://vimeo.



speak more about benefit's:

how long does it take to learn ?
how easy is using it ?
how fast can we type with it ?
etc... (prepare numbers so people be able to compare)

people should feel need this thing...



It doesn't take too long actually. Some weeks at most.
I was using , which is using more layers 
than the common keyboard layouts. but "neo" has a big problem. 
those very free keyboard layouts often don't work, because common 
applications have the power to do the work of the keyboard driver 
(e.g. by binding the "alt"-key to the common usage).
Thus, i am interested in a solution who just works. Maybe writing 
a new hackish keyboard usb driver who is replacing the key codes 
before any other software becomes into play  would solve the 
problem.

Re: DIP 1003: remove `body` as a keyword

[meppl via Digitalmars-d-announce]

Indentation syntax

If we have an optional indentation syntax one day, those 
anonymous looking scopes behind functions may become weird things.


int div(int a, int b)
in { assert(b != 0); }
{
return a / b;
}

indentation:

int div( int a, int b)
in:
assert( b != 0)
:
return a / b



And i like two proposals of this thread here who are not part of 
the DIP:



Kagamin's proposal to just use a shorter keyword than "body" or 
"function".



int div(int a, int b)
in { assert(b != 0); }
do
{
return a / b;
}



Sönke Ludwigs suggestion:

Really nice would be if "in" and "out" would then also take a 
general statement instead of just a block statement, so that a 
syntax like this would become possible for simple contracts:


void foo(int a, int b)
  in assert(0 <= a && a < b);
  out(ret) assert(ret < b);
{
  return b - 1 - a;
}

Re: Beta release DUB 1.0.0-beta.1

[meppl via Digitalmars-d-announce]

On Tuesday, 7 June 2016 at 09:54:19 UTC, Sönke Ludwig wrote:


#!/usr/bin/env dub
/++ dub.sdl:
name "colortest"
dependency "color" version="~>0.0.3"
+/



this is exactly what i could make good use of for my scripting 
stuff. thank you for implementing