On Thursday, 17 November 2016 at 09:40:45 UTC, Carlin St Pierre
wrote:
Is it possible to get the list of usages of a template during
compile time?
For example:
class Foo
{
void bar(T)(T t)
{
}
}
void main()
{
Foo foo = new Foo;
foo.bar(1); // int
On Thursday, 17 November 2016 at 18:40:12 UTC, Suliman wrote:
For example I need to write all logs to file. I see this
function, that seem set some global file name.
"setLogFileSets a log file for disk file logging."
But would it name accessible from anywhere or it would be
visible inl
On Thursday, 17 November 2016 at 18:02:02 UTC, Jesse Phillips
wrote:
On Thursday, 17 November 2016 at 17:54:23 UTC, Suliman wrote:
Ok, but when the logger class may be more helpful that
function usage?
You'd use the logger class when you need to make customizations
or have multiple logging sc
On Thursday, 17 November 2016 at 17:18:27 UTC, Nordlöw wrote:
Why does D need both `@safe`, `@trusted` and `@system` when
Rust seems to get by with only safe (default) and `unsafe`?
https://dlang.org/spec/memory-safe-d.html
http://dlang.org/safed.html
D makes it illegal for @safe code to call
On Thursday, 17 November 2016 at 17:18:27 UTC, Nordlöw wrote:
Why does D need both `@safe`, `@trusted` and `@system` when
Rust seems to get by with only safe (default) and `unsafe`?
I'm pretty sure the Rust `unsafe` just does both D's `@system`
AND `@trusted`.
An unsafe function in Rust is l
On Thursday, 17 November 2016 at 17:54:23 UTC, Suliman wrote:
Ok, but when the logger class may be more helpful that function
usage?
You'd use the logger class when you need to make customizations
or have multiple logging schemes.
I'd expect Vibe.d allows you to override the global logging
On Thursday, 17 November 2016 at 17:54:23 UTC, Suliman wrote:
On Thursday, 17 November 2016 at 17:45:31 UTC, Stefan Koch
wrote:
On Thursday, 17 November 2016 at 17:42:44 UTC, Suliman wrote:
On Thursday, 17 November 2016 at 16:46:37 UTC, Steven
Schveighoffer wrote:
On 11/17/16 11:28 AM, Suliman
On Thursday, 17 November 2016 at 17:45:31 UTC, Stefan Koch wrote:
On Thursday, 17 November 2016 at 17:42:44 UTC, Suliman wrote:
On Thursday, 17 November 2016 at 16:46:37 UTC, Steven
Schveighoffer wrote:
On 11/17/16 11:28 AM, Suliman wrote:
[...]
D does not require classes to write functions.
On Thursday, 17 November 2016 at 17:47:21 UTC, Nordlöw wrote:
On Thursday, 17 November 2016 at 17:33:33 UTC, Stefan Koch
wrote:
Memory is inherently unsafe. But it can be treated in a safe
way.
A language that does not allow you to express a middle ground
will have a lot of unsafe code that cou
On Thursday, 17 November 2016 at 17:33:33 UTC, Stefan Koch wrote:
Memory is inherently unsafe. But it can be treated in a safe
way.
A language that does not allow you to express a middle ground
will have a lot of unsafe code that could arguably be seen as
safe.
So in what way would, for insta
On Thursday, 17 November 2016 at 17:42:44 UTC, Suliman wrote:
On Thursday, 17 November 2016 at 16:46:37 UTC, Steven
Schveighoffer wrote:
On 11/17/16 11:28 AM, Suliman wrote:
[...]
D does not require classes to write functions. All a class
member function is anyway is a function with an impli
On Thursday, 17 November 2016 at 16:46:37 UTC, Steven
Schveighoffer wrote:
On 11/17/16 11:28 AM, Suliman wrote:
There is some functions that can be called without creation of
class.
For example: http://vibed.org/api/vibe.core.log/
As I understand I can create write log in two way. First
creat
On Thursday, 17 November 2016 at 17:29:20 UTC, Nordlöw wrote:
On Thursday, 17 November 2016 at 17:27:01 UTC, Stefan Koch
wrote:
It allows encapsulating unsafe operations in safely-callable
wrappers.
So is this a limitation in Rust? If so, could you give a more
concrete D code example that can
On Thursday, 17 November 2016 at 17:27:01 UTC, Stefan Koch wrote:
It allows encapsulating unsafe operations in safely-callable
wrappers.
So is this a limitation in Rust? If so, could you give a more
concrete D code example that cannot be implemented with only two
safety levels?
On Thursday, 17 November 2016 at 17:18:27 UTC, Nordlöw wrote:
Why does D need both `@safe`, `@trusted` and `@system` when
Rust seems to get by with only safe (default) and `unsafe`?
https://dlang.org/spec/memory-safe-d.html
http://dlang.org/safed.html
It allows encapsulating unsafe operations
Why does D need both `@safe`, `@trusted` and `@system` when Rust
seems to get by with only safe (default) and `unsafe`?
https://dlang.org/spec/memory-safe-d.html
http://dlang.org/safed.html
Does LDC have more diagnostics than DMD, typically unused
imports, variables, etc?
On 11/17/16 11:28 AM, Suliman wrote:
There is some functions that can be called without creation of class.
For example: http://vibed.org/api/vibe.core.log/
As I understand I can create write log in two way. First create instance
of Logger, second simply call function.
Why it's done so? Just as
There is some functions that can be called without creation of
class.
For example: http://vibed.org/api/vibe.core.log/
As I understand I can create write log in two way. First create
instance of Logger, second simply call function.
Why it's done so? Just as shortcut? But is I create class it'
On Tuesday, 1 November 2016 at 22:01:23 UTC, Alfred Newman wrote:
Greetings,
I need some help with dub libraries.
[...]
test.d assumes that sqlite.d is given on the same compile
command-line.
This is the case when sqlite-d is build as a stand-alone app.
If you want to integrate it I advise
On Thursday, 17 November 2016 at 09:40:45 UTC, Carlin St Pierre
wrote:
Is it possible to get the list of usages of a template during
compile time?
For example:
class Foo
{
void bar(T)(T t)
{
}
}
void main()
{
Foo foo = new Foo;
foo.bar(1); // int
Is it possible to get the list of usages of a template during
compile time?
For example:
class Foo
{
void bar(T)(T t)
{
}
}
void main()
{
Foo foo = new Foo;
foo.bar(1); // int
foo.bar(2f); // float
foo.bar("3"); // string
}
// pragma(ms
On Wednesday, 16 November 2016 at 22:43:55 UTC, lafoldes wrote:
Hi,
I'd like to create a UTF16 text file on Windows 7, using
std.stdio.File and std.stdio.File.write... functions (so no
binary write, no Win32 functions).
I was experimenting with variations of this code…:
import std.stdio;
in
23 matches
Mail list logo
