| [package] | |
| name = "test" | |
| version = "0.1.0" | |
| authors = ["YOU <[email protected]>"] | |
| edition = "2018" | |
| [lib] | |
| crate-type = ["cdylib"] |
| #ifndef RANGE_HPP_ | |
| #define RANGE_HPP_ | |
| template<typename T> class RangeIterator; | |
| template<typename T> | |
| class Range | |
| { | |
| T _start, _end, _step; |
Below is my understanding of affine types and how they help us in Rust (unsure if I got this right - please correct if I am talking nonsense).
The issue is... How can we use the power of a type system so a compiler will block us from doing this wrong sequence of calls?
FILE *fp = NULL;
fclose(fp);
fp = fopen("...");
An idea is to "mirror" the states that the file variable goes through (unused/closed, opened) in the type system:
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm
| import numpy as np | |
| import scipy.linalg.blas | |
| cdef extern from "f2pyptr.h": | |
| void *f2py_pointer(object) except NULL | |
| ctypedef int dgemm_t( | |
| char *transa, char *transb, | |
| int *m, int *n, int *k, | |
| double *alpha, |
| /* compile with: | |
| on linux: gcc -g stack_traces.c | |
| on OS X: gcc -g -fno-pie stack_traces.c | |
| on windows: gcc -g stack_traces.c -limagehlp | |
| */ | |
| #include <signal.h> | |
| #include <stdio.h> | |
| #include <assert.h> |