Re: D for microservices: ldc, rdmd, dub now available on Alpine x86_64

2020-01-17 Thread Newbie2019 via Digitalmars-d-announce

On Tuesday, 5 November 2019 at 02:16:28 UTC, Mathias Lang wrote:

Hi all,
Recently there have been inquiries about support for D on 
Alpine Linux, a distribution mostly used in combination with 
Docker to create lightweight container images for microservices.


At BPF Korea, we're working on a blockchain written in D, and 
wanted to be able to easily test and distribute our node using 
Alpine images, but there was no package for it yet.


However, thanks to the work of many contributors before (Joakim 
Noah, yshui, Petar Kirov/zombinedev, and many others), most of 
the porting was already done and it was just a matter of fixing 
a few small issues and and creating the package definitions.


A package for `dub` (v1.18.0), `dtools` (ddemangle & rdmd), and 
`ldc` (v1.18.0) are now available in the `testing` repository 
of Alpine Linux edge. As `testing` is not enabled by default, 
you will need to specify the repository (or add it to your 
`/etc/apk/repositories`) when installing the packages.

For example:
```
apk --no-cache add -X 
http://dl-cdn.alpinelinux.org/alpine/edge/testing ldc 
ldc-static dtools-rdmd dub

```



this not install the lto static lib,  how can i build lto static 
lib for alpine ?




Re: LDC 1.18.0

2019-10-16 Thread Newbie2019 via Digitalmars-d-announce

On Wednesday, 16 October 2019 at 22:31:41 UTC, kinke wrote:

Glad to announce LDC 1.18:

* Based on D 2.088.1.
* Support for LLVM 9.0, which is used for the prebuilt packages.
* Experimental prebuilt Android armv7a package.
* Bundled dub upgraded to v1.17.0+ with improved LDC support, 
incl. cross-compilation.
* Init symbols of zero-initialized structs are no longer 
emitted.
* druntime: DMD-compatible {load,store}Unaligned and prefetch 
added to core.simd.

* JIT improvements, incl. multi-threaded compilation.
* Support for macOS 10.15 and, on Windows, for Visual Studio 
2019 v16.3.


Full release log and downloads: 
https://github.com/ldc-developers/ldc/releases/tag/v1.18.0


Thanks to all contributors!


Thanks for keep up the good work.

Android CI is really a great for mobile users, I wish some day 
there also include IOS cross build binary package.


Re: LDC 1.18.0-beta1

2019-09-23 Thread Newbie2019 via Digitalmars-d-announce

On Thursday, 12 September 2019 at 23:49:04 UTC, kinke wrote:

Glad to announce the first beta for LDC 1.18:

* Based on D 2.088.0+ (yesterday's stable).
* Bundled dub upgraded to v1.17.0+ with improved LDC support, 
incl. cross-compilation.
* Init symbols of zero-initialized structs are no longer 
emitted.
* druntime: DMD-compatible {load,store}Unaligned and prefetch 
added to core.simd.

* JIT improvements, incl. multi-threaded compilation.

Full release log and downloads: 
https://github.com/ldc-developers/ldc/releases/tag/v1.18.0-beta1


Please help test, and thanks to all contributors!


Thanks for keep the great work.

Maybe  https://github.com/ldc-developers/ldc/issues/3156  should 
in Known issues ?




Re: LDC 1.17.0

2019-09-06 Thread Newbie2019 via Digitalmars-d-announce

On Wednesday, 4 September 2019 at 20:54:40 UTC, kinke wrote:

There's a new v1.17 Termux package for Android.


Thanks for the keep the great work.

without LDC, there is not so much d users.


Re: Ownership and Borrowing in D

2019-07-16 Thread Newbie2019 via Digitalmars-d-announce

On Tuesday, 16 July 2019 at 06:12:42 UTC, Walter Bright wrote:

Now I just have to deliver the goods!


Very exciting about d have the @live and borrow owner feature.

How do you plan to handle move ?  dose it depends on DIP1014 ?


Re: Priority DIP for Draft Review: Argument Ownership and Function Calls

2019-06-28 Thread Newbie2019 via Digitalmars-d-announce

On Wednesday, 26 June 2019 at 10:51:33 UTC, Mike Parker wrote:
Walter has a DIP currently in Draft Review that is a critical 
feature for the implementation of safe ref counting. It needs 
to have priority through the DIP process.


Before I move it to Community Review, it should be vetted for a 
couple of weeks in the Draft Review. Anyone who has the time 
and interest, please cast your eyes upon it and attempt to 
destroy it to the best of your ability:




Even I may not fully understand it, I still vote to support this 
DIPs.


The limits is clear and only effect the "bugs  prone" double 
scope ref code,  this kind code should be addressed anyway.


I do like D have full borrow check/static interface without 
runtime cost very much(the rust style), but we already has 
dip1000 why not make it more safe and move on.