Andrei Alexandrescu via Digitalmars-d
napsal So, pro 24, 2016 v 9∶32 :
Consider:
with (import std.stdio)
int fun(int x/*, File f*/)
{
// f.writeln("In: ", x);
return x * x;
}
Such situations occur during refactorings and code evolution. The
import is no
On Saturday, 24 December 2016 at 20:32:58 UTC, Andrei
Alexandrescu wrote:
Consider:
with (import std.stdio)
int fun(int x/*, File f*/)
{
// f.writeln("In: ", x);
return x * x;
}
Such situations occur during refactorings and code evolution.
The import is no longer used. Should the
On Saturday, 24 December 2016 at 20:32:58 UTC, Andrei
Alexandrescu wrote:
Such situations occur during refactorings and code evolution.
The import is no longer used. Should the compiler flag that as
an error, or leave it be?
please, no. "this is a work for a linter", as Walter likes to say
On Saturday, December 24, 2016 15:32:58 Andrei Alexandrescu via Digitalmars-
d wrote:
> Consider:
>
> with (import std.stdio)
> int fun(int x/*, File f*/)
> {
> // f.writeln("In: ", x);
> return x * x;
> }
>
> Such situations occur during refactorings and code evolution. The import
> is
On 25/12/2016 9:32 AM, Andrei Alexandrescu wrote:
Consider:
with (import std.stdio)
int fun(int x/*, File f*/)
{
// f.writeln("In: ", x);
return x * x;
}
Such situations occur during refactorings and code evolution. The import
is no longer used. Should the compiler flag that as an
On Saturday, 24 December 2016 at 20:32:58 UTC, Andrei
Alexandrescu wrote:
Consider:
with (import std.stdio)
int fun(int x/*, File f*/)
{
// f.writeln("In: ", x);
return x * x;
}
Such situations occur during refactorings and code evolution.
The import is no longer used. Should the
Consider:
with (import std.stdio)
int fun(int x/*, File f*/)
{
// f.writeln("In: ", x);
return x * x;
}
Such situations occur during refactorings and code evolution. The import
is no longer used. Should the compiler flag that as an error, or leave
it be?
Andrei