Hi,
I'm currently making changes to cgdb, and would like to have
someone give a quick view over the lexer rules.
https://github.com/cgdb/cgdb/blob/master/lib/tokenizer/dlexer.l
Having a skim over myself, I see @nogc needs adding, and probably
c_long, cpp_long and other ABI compatibility
On Saturday, 14 November 2015 at 11:30:04 UTC, Walter Bright
wrote:
Like I said, you think the points I raised are all non-issues.
Please don't make assumptions about what I think. What I think is
that for a language that is aligned with C semantics, you can
with reasonable effort generate
On Saturday, 14 November 2015 at 10:44:53 UTC, Iain Buclaw wrote:
Hi,
I'm currently making changes to cgdb, and would like to have
someone give a quick view over the lexer rules.
https://github.com/cgdb/cgdb/blob/master/lib/tokenizer/dlexer.l
Having a skim over myself, I see @nogc needs
On 11/11/2015 4:19 AM, Walter Bright wrote:
I've looked into generating C code as an output format. I found the problems to
be endemic and working around them was harder than just generating native code:
1. You're at the mercy of bugs in the C compiler you cannot fix.
2. C leaves quite a lot as
On 13/11/2015 14:52, anonymous wrote:
I/we should make an SVG version that uses paths instead of , so
that it doesn't depend on a local font. Maybe agree on the font first,
though.
With the chosen font installed ("Droid Sans", Apache 2.0 licence) the
text balances well (or at least better
Hi everybody,
I have the following question about "by reference" behavior
related to structs.
I have a struct, say S, which contains a member of reference type
struct S
{
int[] member;
}
and I have a main, for testing:
void main()
{
S s; // = new S();
s.arr = [1,2,3];
On 11/14/2015 1:58 AM, Ola Fosheim Grøstad wrote:
[...]
Like I said, you think the points I raised are all non-issues. You'll change
your mind once you try to implement one, and then try to support it with a
diverse group of customers.
> C99 defines [...]
I just have to laugh. You even
On Friday, 13 November 2015 at 23:12:34 UTC, Steven Schveighoffer
wrote:
If you cannot update to the latest compiler
Didn't realised this feature is so new to the compiler. In my
case, it is no problem to update the compiler, and I will.
Thanks!
On Saturday, 14 November 2015 at 03:10:17
On Saturday, 14 November 2015 at 06:16:15 UTC, Walter Bright
wrote:
True, but that doesn't support your assertion that transpiling
to C produces better C interop.
Setting aside compatibility with the C preprocessor, I've asked
for a single instance where a language that transpiles to C has
On 11/14/2015 12:06 AM, Ola Fosheim Grøstad wrote:
I'm not sure if it reasonable to set aside the preprocessor,
If your new language doesn't have the C preprocessor in it, then you must set it
aside. If it does have a C preprocessor in it, then it really isn't a new
language at all, it's
On Saturday, 14 November 2015 at 09:58:19 UTC, Ola Fosheim
Grøstad wrote:
http://www.mercurylang.org/backends.html
Btw, didn't Ali convert his book on D using princeXML?
princeXML is written in Mercury:
https://en.wikipedia.org/wiki/Prince_(software)
On 14-Nov-2015 02:10, Andrei Alexandrescu wrote:
I created a simple persistent list with reference counting and custom
allocation at http://dpaste.dzfl.pl/0981640c2835. It's a good
illustration of a number of issues. In particular, each cast must be
properly explained.
Here's my exegesis:
On Saturday, 14 November 2015 at 08:28:08 UTC, Walter Bright
wrote:
If your new language doesn't have the C preprocessor in it,
then you must set it aside. If it does have a C preprocessor in
it, then it really isn't a new language at all, it's just a C
permutation.
But you can do code gen
The book was delivered today! The size is similar to the C++
Primer. But I don't like the quality of the cover. Looks like
they have used a blunt blade to cut it and there are damages at
the adges.
Dne 13.11.2015 v 15:52 anonymous via Digitalmars-d-announce napsal(a):
> On 13.11.2015 15:22, Andrei Alexandrescu wrote:
>> By my count:
>>
>> * 1.1:xxx
>> * 1.2:xxx
>> * 2: xxx
>> * 3: xx
>> * 3, change font:
On Saturday, 14 November 2015 at 10:46:57 UTC, Alex wrote:
Hi everybody,
I have the following question about "by reference" behavior
related to structs.
I have a struct, say S, which contains a member of reference
type
struct S
{
int[] member;
}
and I have a main, for testing:
void
https://issues.dlang.org/show_bug.cgi?id=15335
Issue ID: 15335
Summary: getSymbolsByUDA fails if type has private members
Product: D
Version: D2
Hardware: x86_64
OS: Linux
Status: NEW
Severity: enhancement
https://issues.dlang.org/show_bug.cgi?id=15338
Vladimir Panteleev changed:
What|Removed |Added
Priority|P1 |P3
Hi everyone,
Just looked at the vision for this half, and I had an idea pop in
my head. Before I get to that idea, let me explain what I think
might be an issue with it as-is.
I've consistently seen D's participation metrics marked by the
number of pull requests created and closed, which is
https://issues.dlang.org/show_bug.cgi?id=15339
Issue ID: 15339
Summary: std.datetime: document DST handling
Product: D
Version: D2
Hardware: x86_64
OS: Linux
Status: NEW
Severity: enhancement
On Saturday, 14 November 2015 at 23:20:08 UTC, Andrei
Alexandrescu wrote:
On 11/14/15 5:49 PM, Timon Gehr wrote:
It's supposed to guarantee that the given reference is not
used to
transitively mutate the object. The casts violate this.
I think that semantics needs to change. Specifically,
On Saturday, 14 November 2015 at 14:56:57 UTC, maik klein wrote:
http://dlang.org/phobos/std_experimental_allocator.html
I am not sure what the plan is but it seems to me that the
standard library could make use of the "theAllocator" for
allocation and also allow you to swap in different
David Nadlinger writes:
> On Friday, 13 November 2015 at 18:40:06 UTC, Iain Buclaw wrote:
>> There may be a few other holes between how Fibers and EH interact.
>>
>> https://github.com/D-Programming-Language/druntime/commit/f6633abb43ea1f2464d3a772b8f8fe78216ffd8e
>
> The
On Saturday, 14 November 2015 at 16:05:10 UTC, Andrei
Alexandrescu wrote:
Technically, that clearly works. There's a problem with scaling
it up:
COMPOSITION
Disallowing immutable(RC!T) in favor of RC!(immutable T)
effectively disables composition of larger immutable objects
from smaller
On 09/11/15 04:38, Richard Davies wrote:
On Friday, 18 September 2015 at 03:19:26 UTC, Nick B wrote:
On Thursday, 17 September 2015 at 23:53:30 UTC, Anthony Di Franco wrote:
I read the whole book and did not regret it at all, but I was already
looking for good interval arithmetic
On Saturday, 14 November 2015 at 13:46:32 UTC, Russel Winder
wrote:
On Sat, 2015-11-14 at 10:47 +1000, Manu via Digitalmars-d wrote:
[…]
I'd love to read a revised edition of that page! :)
So write it, and do the pull request. It doesn't matter if it
is any good or not, what matters is
https://issues.dlang.org/show_bug.cgi?id=15338
Issue ID: 15338
Summary: COFF EH tables are not linker-GC-able
Product: D
Version: D2
Hardware: x86_64
OS: Windows
Status: NEW
Keywords: bare-metal,
https://issues.dlang.org/show_bug.cgi?id=15331
--- Comment #4 from Chris Wright ---
> No I wont.
If you're leaving it to the other person to file the new bug, you could perhaps
leave it to them to resolve the issue as invalid. There's far less chance of a
real problem
https://issues.dlang.org/show_bug.cgi?id=15340
Kenji Hara changed:
What|Removed |Added
Keywords||pull
--- Comment #1 from
https://issues.dlang.org/show_bug.cgi?id=15340
Issue ID: 15340
Summary: Spurious "overlapped default initialization" errors
with auto fields
Product: D
Version: D2
Hardware: All
OS: All
Status:
On Saturday, 14 November 2015 at 03:40:08 UTC, Walter Bright
wrote:
The current state can be found here:
https://www.youtube.com/watch?v=IkwaV6k6BmM
slides:
http://www.walterbright.com/cppint.pdf
If someone would care to turn that into a pull request for
On Saturday, 14 November 2015 at 12:46:21 UTC, Relja wrote:
I've got this strange compile error using
std.conv.to!string(double[3]) - or any static array type. It's
called in toString override function of a template matrix
class, I'm building as a D learning project.
[...]
Maybe try to use
This is a classic topic in .learn when someone tries to declare a
static array over 10 MB. Are there other limits ? Are they worth
a new documentation page ?
For example, FPC has
http://www.freepascal.org/docs-html/3.0.0/prog/progap3.html
On Fri, 2015-11-13 at 19:40 -0800, Walter Bright via Digitalmars-d
wrote:
> […]
>
> that would be most appreciated!
Or you could do it based on your material, no?
--
Russel.
=
Dr Russel Winder t: +44 20 7585 2200
On 11/13/2015 07:28 PM, Jakob Ovrum wrote:
On Friday, 13 November 2015 at 23:10:04 UTC, Andrei Alexandrescu wrote:
* Lines 11-12: I came to terms with the notion that some types cannot
be made immutable. We've been trying to do reference counting on
immutable objects for a long time. It's time
On 11/14/2015 4:35 AM, cym13 wrote:
Off-topic, but I'd like to know more about that. Did you by any chance ever
wrote a blog post of some sort describing thoses issues?
Sorry, it was a couple years ago, I don't recall the specifics.
On 11/14/2015 3:39 AM, Ola Fosheim Grøstad wrote:
What I think is that for a
language that is aligned with C semantics, you can with reasonable effort
generate good quality C99 code.
https://www.youtube.com/watch?v=YlVDGmjz7eM
:-)
On Saturday, 14 November 2015 at 13:33:49 UTC, Fer22f wrote:
Hello! I'm starting to make some simple command line programs
and one thing I miss from C is a function for getting one
character from the input. This is for example, an "Press Any
Key Program".
Anyone that has more experience can
On Saturday, 14 November 2015 at 12:55:52 UTC, BBaz wrote:
On Saturday, 14 November 2015 at 12:46:21 UTC, Relja wrote:
I've got this strange compile error using
std.conv.to!string(double[3]) - or any static array type. It's
called in toString override function of a template matrix
class, I'm
On 14.11.2015 15:17, Relja wrote:
- std.conv.to!string() works on a static array, when called directly on
the array object, but gives the compile error when called on the
returning object from a function.
[...]
void main() {
getFloat3().to!string; // does not compile
(new
http://wiki.dlang.org/DIP85
This DIP proposes an officially sanctioned way to initialize
const members (or mutable members of const structs) lazily by
allowing limited mutation of const objects.
Destroy!
On Saturday, 14 November 2015 at 14:30:06 UTC, anonymous wrote:
On 14.11.2015 15:17, Relja wrote:
- std.conv.to!string() works on a static array, when called
directly on
the array object, but gives the compile error when called on
the
returning object from a function.
[...]
void main() {
P.S. another problem with `RC!(immutable T)` is that it actually
must be `shared(RC!(immutable T)` to be provide @safe API.
I don't think immutable should be something casual and widespread
in most designs at all. It is a very restrictive qualifier with
an extremely narrow use case, trying to retro-fit it to be easy
to use and compose tends to do more harm than actually going with
mutable instead.
All trouble
On Saturday, 14 November 2015 at 11:30:04 UTC, Walter Bright
wrote:
Guess what happened when I found out that people were relying
on bugs in gcc's preprocessor, not to mention all of its
non-standard behavior.
Off-topic, but I'd like to know more about that. Did you by any
chance ever wrote
On Sat, 2015-11-14 at 10:47 +1000, Manu via Digitalmars-d wrote:
> […]
> I'd love to read a revised edition of that page! :)
So write it, and do the pull request. It doesn't matter if it is any
good or not, what matters is activity. All the waffling and wailing on
the mailing list results in f###
On Saturday, 14 November 2015 at 13:33:49 UTC, Fer22f wrote:
Hello! I'm starting to make some simple command line programs
and one thing I miss from C is a function for getting one
character from the input. This is for example, an "Press Any
Key Program".
Anyone that has more experience can
On Friday, 13 November 2015 at 18:40:06 UTC, Iain Buclaw wrote:
There may be a few other holes between how Fibers and EH
interact.
https://github.com/D-Programming-Language/druntime/commit/f6633abb43ea1f2464d3a772b8f8fe78216ffd8e
The SJLJ stack switching should probably be added to this
On 11/14/2015 03:41 AM, Namal wrote:
The book was delivered today! The size is similar to the C++ Primer. But
I don't like the quality of the cover. Looks like they have used a blunt
blade to cut it and there are damages at the adges.
That's not good. :( I have a few copies here with me, which
On 11/13/2015 06:26 PM, Ali Çehreli wrote:
On 11/13/2015 03:10 PM, Andrei Alexandrescu wrote:
> at http://dpaste.dzfl.pl/0981640c2835
> * Lines 11-12: I came to terms with the notion that some types cannot be
> made immutable.
Could constructor qualifiers help in such cases? I would like
On Saturday, 14 November 2015 at 11:48:42 UTC, Mike Parker wrote:
So, I create a first var of type S, then the second and copied
the first into the second. The behavior is like intended, the
array inside the struct is copied. But this is a deep copy, as
the third block shows. If I change the
On 11/14/2015 08:47 AM, Russel Winder via Digitalmars-d wrote:
On Fri, 2015-11-13 at 19:40 -0800, Walter Bright via Digitalmars-d
wrote:
[…]
that would be most appreciated!
Or you could do it based on your material, no?
I take it there's a bit of sarcasm there, so probably it's worth
I've got this strange compile error using
std.conv.to!string(double[3]) - or any static array type. It's
called in toString override function of a template matrix class,
I'm building as a D learning project.
Here is the toString method:
override string toString() const
{
string outs;
On Saturday, 14 November 2015 at 00:37:51 UTC, Manu wrote:
In the meantime, there probably needs to be strong warnings
about violating attributes, and if patterns have emerged that
rely on violating such attributes, we should publish a
recommended alternative.
One pattern that comes to mind
Hello! I'm starting to make some simple command line programs and
one thing I miss from C is a function for getting one character
from the input. This is for example, an "Press Any Key Program".
Anyone that has more experience can point me into a solution that
is not deprecated? I haven't
On Saturday, 14 November 2015 at 05:44:44 UTC, Anonymous wrote:
I was playing with some code someone posted on the forum that
involved opDispatch and compile time parameters. I pasted it in
a file named templOpDispatch.d, ran it, and got an error. Then
I noticed if I renamed the file it
On Saturday, 14 November 2015 at 12:14:42 UTC, Handyman wrote:
The D docs seem very thorough and complete to me but less
accessible in comparison to, e.g., Perl docs, Php docs, or Ruby
docs. In particular I have difficulties in understanding the
headers of the standard library function
Dan Olson writes:
> Johannes Pfau writes:
>
>> Am Thu, 12 Nov 2015 09:59:14 -0800
>> schrieb Dan Olson :
>>
>>> Johannes Pfau writes:
>>> > To expand on this: I think we'd prefer one __d_personality_v0 which
>>> > is
http://dlang.org/phobos/std_experimental_allocator.html
I am not sure what the plan is but it seems to me that the
standard library could make use of the "theAllocator" for
allocation and also allow you to swap in different allocators.
So could it then be possible to completely bypass the GC
On Saturday, 14 November 2015 at 05:44:44 UTC, Anonymous wrote:
Then running 'rdmd templOpDispatch.d' produces:
std.process.ProcessException@std\process.d(568): Failed to
spawn new process (The requested operation requires elevation.)
This is a Windows quirk. When they introduced UAC in
I have some binary files that I'm reading. At compile time it's
unknown what types I'm reading, and if they're strings, how it's
encoded.
I'm doing something like this:
Variant value;
switch(type)
{
...
case Type.STRING:
value = cast(dchar[])[];
On Saturday, 14 November 2015 at 14:30:33 UTC, Marc Schütz wrote:
http://wiki.dlang.org/DIP85
This DIP proposes an officially sanctioned way to initialize
const members (or mutable members of const structs) lazily by
allowing limited mutation of const objects.
Destroy!
I'm just right now
On Saturday, 14 November 2015 at 11:39:12 UTC, Brian Schott wrote:
On Saturday, 14 November 2015 at 10:44:53 UTC, Iain Buclaw
wrote:
Hi,
I'm currently making changes to cgdb, and would like to have
someone give a quick view over the lexer rules.
On 11/14/2015 07:28 AM, Ali Çehreli wrote:
Print-on-demand books are non-returnable.
Correction: They are non-returnable in general, depending on where they
were printed.
The other ISBN of this particular book is still print-on-demand but it
is returnable just like any other book:
On 11/13/2015 06:36 PM, Steven Schveighoffer wrote:
On 11/13/15 6:10 PM, Andrei Alexandrescu wrote:
I created a simple persistent list with reference counting and custom
allocation at http://dpaste.dzfl.pl/0981640c2835. It's a good
illustration of a number of issues. In particular, each cast
On 11/13/2015 06:41 PM, Timon Gehr wrote:
On 11/14/2015 12:10 AM, Andrei Alexandrescu wrote:
* Lines 6: By construction the list doesn't work with mutable objects.
=(
I've decided persistent lists with mutable elements just too weird to
endorse. Lisp allows them but every time it mentions
On Saturday, 14 November 2015 at 17:01:53 UTC, Loretta wrote:
On Saturday, 14 November 2015 at 13:46:32 UTC, Russel Winder
wrote:
On Sat, 2015-11-14 at 10:47 +1000, Manu via Digitalmars-d
wrote:
[…]
I'd love to read a revised edition of that page! :)
So write it, and do the pull request. It
On Friday, 13 November 2015 at 21:30:35 UTC, Rory McGuire wrote:
On Tue, Nov 10, 2015 at 6:56 PM, Steven Schveighoffer via
Digitalmars-d < digitalmars-d@puremagic.com> wrote:
To install a new compiler I just download the latest .tar.xz
and place in /usr/local/dmd/; and then rename "dmd2"
https://issues.dlang.org/show_bug.cgi?id=15336
Chris Wright changed:
What|Removed |Added
See Also|
https://issues.dlang.org/show_bug.cgi?id=15331
Chris Wright changed:
What|Removed |Added
See Also|
On Thursday, 12 November 2015 at 06:52:36 UTC, Suliman wrote:
On Thursday, 1 August 2013 at 17:29:00 UTC, Suliman wrote:
Would it be possible to create block "communities" on
dlang.org site and put there links to national language
communities?
We are back online. Still site have a lot of
https://issues.dlang.org/show_bug.cgi?id=15336
Issue ID: 15336
Summary: std.json: opIn undocumented for JSONValue
Product: D
Version: D2
Hardware: x86_64
OS: Linux
Status: NEW
Severity: normal
On 14.11.2015 15:40, Relja wrote:
float[3] array;
array.to!string; // compiles
Alright, full test case:
import std.conv;
float[3] getFloat3() {
return [1, 2, 3];
}
void main() {
getFloat3().to!string; // does not compile
float[3] a;
a.to!string; // compiles
}
On Saturday, 14 November 2015 at 17:03:21 UTC, Reg wrote:
On Saturday, 14 November 2015 at 17:01:53 UTC, Loretta wrote:
On Saturday, 14 November 2015 at 13:46:32 UTC, Russel Winder
wrote:
On Sat, 2015-11-14 at 10:47 +1000, Manu via Digitalmars-d
wrote:
[...]
So write it, and do the pull
On Saturday, 14 November 2015 at 13:46:32 UTC, Russel Winder
wrote:
On Sat, 2015-11-14 at 10:47 +1000, Manu via Digitalmars-d wrote:
[…]
I'd love to read a revised edition of that page! :)
So write it, and do the pull request. It doesn't matter if it
is any good or not, what matters is
On 14.11.2015 15:55, Charles wrote:
I know there's safeDecode, but I'm also fairly confident that all
strings can decode safely, already, and if it isn't I'd want an
exception thrown from it.
Documentation [1] says "The input to this function MUST be validly
encoded." It says nothing about an
BTW I was slightly inaccurate: it doesn't *require* a library to
do this, you just need to disable buffering. But the getc
function itself doing that is dependent on some library
implementation.
On Windows for example you need to call this function and turn
off line input:
On 11/14/2015 03:55 PM, Timon Gehr wrote:
On 11/14/2015 12:10 AM, Andrei Alexandrescu wrote:
...
* Lines 11-12: I came to terms with the notion that some types cannot be
made immutable. We've been trying to do reference counting on immutable
objects for a long time. It's time to acknowledge
https://issues.dlang.org/show_bug.cgi?id=15337
Issue ID: 15337
Summary: Make Funkwerk's depend a part of the standard tools
distribution
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
On 11/14/2015 09:42 PM, Andrei Alexandrescu wrote:
On 11/14/2015 03:36 PM, Timon Gehr wrote:
Right, because e.g. whether the elements are reference counted or traced
should totally completely change the required container semantics for
the problem at hand! This does not make any sense, unless
On 11/13/2015 07:51 AM, Stefan wrote:
On Thursday, 12 November 2015 at 23:08:57 UTC, Jakob Ovrum wrote:
> [...dependency check...]
It can be implemented as an external tool with the -deps compiler switch.
there is depend [1].
It warns about cycles and unintended dependencies if you
On 11/14/2015 05:04 PM, Timon Gehr wrote:
We have had the discussion you are asking for before, and you have
decided to ignore it, with the justification that this was how you
decided and a vague appeal to emotion. I usually don't operate under
the assumption that identical experiments lead to
On Friday, 13 November 2015 at 14:22:32 UTC, Andrei Alexandrescu
wrote:
On 11/04/2015 04:30 AM, Andrei Alexandrescu wrote:
[...]
By my count:
* 1.1:xxx
* 1.2:xxx
* 2: xxx
* 3: xx
* 3, change font:
On 11/14/2015 10:59 PM, Andrei Alexandrescu wrote:
On 11/14/2015 03:55 PM, Timon Gehr wrote:
On 11/14/2015 12:10 AM, Andrei Alexandrescu wrote:
...
* Lines 11-12: I came to terms with the notion that some types cannot be
made immutable. We've been trying to do reference counting on immutable
On Saturday, 14 November 2015 at 16:19:13 UTC, Walter Bright
wrote:
On 11/14/2015 3:39 AM, Ola Fosheim Grøstad wrote:
What I think is that for a
language that is aligned with C semantics, you can with
reasonable effort
generate good quality C99 code.
On 14.11.2015 13:07, Alix Pexton wrote:
I have a personal dislike of narrow D glyphs, so I'd like to move the
swoosh a small distance from the spire to add a horizontal hint to the
outline.
I think the text could be closer to the glyph, and higher, such that the
D is in about the 2-o'clock
https://issues.dlang.org/show_bug.cgi?id=15331
--- Comment #3 from bb.t...@gmx.com ---
(In reply to Chris Wright from comment #2)
> Next time, please open the new bug before resolving the old one. There's a
> real problem, and it's not resolved. By creating the new bug first, you can
> also
On 11/14/2015 04:45 PM, Andrei Alexandrescu wrote:
On 11/13/2015 06:41 PM, Timon Gehr wrote:
On 11/14/2015 12:10 AM, Andrei Alexandrescu wrote:
* Lines 6: By construction the list doesn't work with mutable objects.
=(
I've decided persistent lists with mutable elements just too weird to
On Saturday, 14 November 2015 at 16:27:17 UTC, Dicebot wrote:
All trouble comes from trying to use physical immutable as
logical one while still pretending it gives physical
guarantees. Even if existing immutability is not widely
applicable, I'd prefer to have narrow applicability over wide
https://issues.dlang.org/show_bug.cgi?id=15333
ag0ae...@gmail.com changed:
What|Removed |Added
Hardware|x86 |All
OS|Mac OS X
On Saturday, 14 November 2015 at 18:52:54 UTC, anonymous wrote:
On 14.11.2015 15:40, Relja wrote:
[...]
Alright, full test case:
import std.conv;
[...]
Great explanation! Thank you!
On 11/14/2015 05:05 PM, Andrei Alexandrescu wrote:
Technically, that clearly works. There's a problem with scaling it up:
COMPOSITION
...
Composition matters.
Disallowing immutable(RC!T) in favor of RC!(immutable T) effectively
disables composition of larger immutable objects from smaller
On 11/14/2015 12:10 AM, Andrei Alexandrescu wrote:
...
* Lines 11-12: I came to terms with the notion that some types cannot be
made immutable. We've been trying to do reference counting on immutable
objects for a long time. It's time to acknowledge that true immutability
(which the immutable
On 11/14/2015 03:36 PM, Timon Gehr wrote:
Right, because e.g. whether the elements are reference counted or traced
should totally completely change the required container semantics for
the problem at hand! This does not make any sense, unless you are saying
that nobody should actually use the
On Saturday, 14 November 2015 at 20:05:45 UTC, Adam D. Ruppe
wrote:
Notably, it is pretty common on Windows, but requires an add-on
library like ncurses on Linux.
https://github.com/adamdruppe/arsd/blob/master/terminal.d
Yea, I always though it would be kinda different between
platforms but
On Saturday, 14 November 2015 at 13:53:50 UTC, BBaz wrote:
stdin.readf("%c", );
writeln(c);
Nope. In *nix this works? In Windows I still need to hit enter,
and the character is the first one of the line I entered.
https://issues.dlang.org/show_bug.cgi?id=15250
--- Comment #3 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/D-Programming-Language/dlang.org
https://github.com/D-Programming-Language/dlang.org/commit/f5d948df33498aec6f1cd9692244e8bce77e6129
Document
https://issues.dlang.org/show_bug.cgi?id=10233
Issue 10233 depends on issue 15250, which changed state.
Issue 15250 Summary: Grammar does not contain rules for multiple slices in an
index expression
https://issues.dlang.org/show_bug.cgi?id=15250
What|Removed
On 11/14/15 5:49 PM, Timon Gehr wrote:
It's supposed to guarantee that the given reference is not used to
transitively mutate the object. The casts violate this.
I think that semantics needs to change. Specifically, either we add a
@mutable attribute (which means const doesn't apply to fields
On 11/14/2015 11:37 PM, Andrei Alexandrescu wrote:
On 11/14/2015 05:04 PM, Timon Gehr wrote:
We have had the discussion you are asking for before, and you have
decided to ignore it, with the justification that this was how you
decided and a vague appeal to emotion. I usually don't operate under
1 - 100 of 106 matches
Mail list logo