On 9/9/16 11:32 AM, Nick Sabalausky wrote:
On 09/08/2016 06:22 PM, Nick Sabalausky wrote:
On 09/08/2016 06:13 PM, Steven Schveighoffer wrote:
On 9/8/16 6:02 PM, Nick Sabalausky wrote:
I'm getting deprecation messages ("Package...not accessible here,
perhaps add static import") when simply
On 09/09/2016 12:35 PM, pineapple wrote:
On Friday, 9 September 2016 at 11:54:42 UTC, Steven Schveighoffer wrote:
Can you demonstrate the issue? I have never heard of this. imports
should work when done inside a function.
-Steve
Tried and failed to reproduce with a simple example, but any
On Friday, 9 September 2016 at 11:54:42 UTC, Steven Schveighoffer
wrote:
Can you demonstrate the issue? I have never heard of this.
imports should work when done inside a function.
-Steve
Tried and failed to reproduce with a simple example, but any time
I've tried doing it in the code I'm
On 09/08/2016 06:22 PM, Nick Sabalausky wrote:
On 09/08/2016 06:13 PM, Steven Schveighoffer wrote:
On 9/8/16 6:02 PM, Nick Sabalausky wrote:
I'm getting deprecation messages ("Package...not accessible here,
perhaps add static import") when simply trying to use fully-qualified
symbol names to
On 9/8/16 6:26 PM, Nick Sabalausky wrote:
On 09/08/2016 06:22 PM, Nick Sabalausky wrote:
On 09/08/2016 06:13 PM, Steven Schveighoffer wrote:
And
there are still some straggling bugs which cause this message to be
erroneously printed.
I'm pretty sure I've hit one of those :( Can't be certain
On 9/9/16 5:38 AM, pineapple wrote:
On Thursday, 8 September 2016 at 22:13:26 UTC, Steven Schveighoffer wrote:
I posted an article on this:
http://www.schveiguy.com/blog/2016/03/import-changes-in-d-2-071/
Regarding that article:
Another import-related bug fix is to prevent unintentional
On Thursday, 8 September 2016 at 22:13:26 UTC, Steven
Schveighoffer wrote:
I posted an article on this:
http://www.schveiguy.com/blog/2016/03/import-changes-in-d-2-071/
-Steve
Regarding that article:
Another import-related bug fix is to prevent unintentional
hijacking of symbols inside a
On Thursday, September 08, 2016 18:26:40 Nick Sabalausky via Digitalmars-d-
learn wrote:
> On 09/08/2016 06:22 PM, Nick Sabalausky wrote:
> > On 09/08/2016 06:13 PM, Steven Schveighoffer wrote:
> >> And
> >> there are still some straggling bugs which cause this message to be
> >> erroneously
On 09/08/2016 03:22 PM, Nick Sabalausky wrote:
On 09/08/2016 06:13 PM, Steven Schveighoffer wrote:
On 9/8/16 6:02 PM, Nick Sabalausky wrote:
I'm getting deprecation messages ("Package...not accessible here,
perhaps add static import") when simply trying to use fully-qualified
symbol names to
On 09/08/2016 06:22 PM, Nick Sabalausky wrote:
On 09/08/2016 06:13 PM, Steven Schveighoffer wrote:
And
there are still some straggling bugs which cause this message to be
erroneously printed.
I'm pretty sure I've hit one of those :( Can't be certain though until I
examine my specific case
On 09/08/2016 06:13 PM, Steven Schveighoffer wrote:
On 9/8/16 6:02 PM, Nick Sabalausky wrote:
I'm getting deprecation messages ("Package...not accessible here,
perhaps add static import") when simply trying to use fully-qualified
symbol names to disambiguate a symbol. Is this really intended?
On 9/8/16 6:13 PM, Steven Schveighoffer wrote:
On 9/8/16 6:02 PM, Nick Sabalausky wrote:
I'm getting deprecation messages ("Package...not accessible here,
perhaps add static import") when simply trying to use fully-qualified
symbol names to disambiguate a symbol. Is this really intended?
Yes.
On 9/8/16 6:02 PM, Nick Sabalausky wrote:
I'm getting deprecation messages ("Package...not accessible here,
perhaps add static import") when simply trying to use fully-qualified
symbol names to disambiguate a symbol. Is this really intended?
Yes.
It's difficult to attribute the message
On 09/08/2016 03:02 PM, Nick Sabalausky wrote:
I'm getting deprecation messages ("Package...not accessible here,
perhaps add static import") when simply trying to use fully-qualified
symbol names to disambiguate a symbol. Is this really intended?
Sounds like the recent changes in 2.071:
14 matches
Mail list logo