Skip to content

Commit

Permalink
Fix build of verifast-rust
Browse files Browse the repository at this point in the history
  • Loading branch information
ia0 committed Oct 24, 2024
1 parent e2df5da commit 088d250
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 2 deletions.
5 changes: 4 additions & 1 deletion .github/workflows/book.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@ name: Deploy site

on:
push:
pull_request:
schedule:
- cron: '0 2 * * *'

Expand All @@ -29,6 +30,7 @@ jobs:
with:
path: ./public
deploy:
if: ${{ github.event_name != 'pull_request' }}
needs: build

permissions:
Expand All @@ -41,6 +43,7 @@ jobs:

runs-on: ubuntu-latest
steps:
- run: echo '${{ toJSON(github) }}'
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v4 # or specific "vX.X.X" version tag for this action
uses: actions/deploy-pages@v4 # or specific "vX.X.X" version tag for this action
2 changes: 1 addition & 1 deletion content/meetings/verifast-rust.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
+++
title = "Towards Sound `unsafe` Rust"
date = 2024-10-28T19:00:00+01:00 (Paris/Zurich)
date = 2024-10-28T19:00:00+01:00 # (Paris/Zurich)
+++

Rust guarantees memory safety and data race freedom through its type checker, which enforces *ownership* and *borrowing* rules. However, adhering strictly to these rules can limit expressiveness and restrict certain high-performance implementations. To address this limitation, Rust allows programmers to relax some type system checks within `unsafe` blocks. The challenge, however, is that maintaining type system invariants within these relaxed blocks becomes the programmer's responsibility.
Expand Down

0 comments on commit 088d250

Please sign in to comment.