upstream/mercurial-mirror Files · rust/hg-core/src/dirstate/mod.rs

py3: hack around inconsistency of type of name passed to DNSQuestion...

py3: hack around inconsistency of type of name passed to DNSQuestion I don't like this patch but this is the easiest way I could fix it. There are some callers which pass name which is bytes, some pass name which is str. I just encode() that if that's str. This does makes test-paths.t pass, but I am not confident whether the whole of zeroconf will work on py3 or not. Differential Revision: https://phab.mercurial-scm.org/D6511

Raphaël Gomès - - Load All Authors

File last commit:

r42736:2dcee649 default


                r42754:8306b6c2

default

Download file

             mod.rs
        
                    36 lines
            
             | 852 B
            
                | application/rls-services+xml
            
             |
                RustLexer
            
             / rust / hg-core / src / dirstate / mod.rs
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      pub mod dirs_multiset;

      pub mod parsers;

      #[derive(Debug, PartialEq, Copy, Clone)]

      pub struct DirstateParents<'a> {

          pub p1: &'a [u8],

          pub p2: &'a [u8],

      }

      /// The C implementation uses all signed types. This will be an issue

      /// either when 4GB+ source files are commonplace or in 2038, whichever

      /// comes first.

      #[derive(Debug, PartialEq)]

      pub struct DirstateEntry {

          pub state: i8,

          pub mode: i32,

          pub mtime: i32,

          pub size: i32,

      }

      pub type DirstateVec = Vec<(Vec<u8>, DirstateEntry)>;

      #[derive(Debug, PartialEq)]

      pub struct CopyVecEntry<'a> {

          pub path: &'a [u8],

          pub copy_path: &'a [u8],

      }

      pub type CopyVec<'a> = Vec<CopyVecEntry<'a>>;

      /// The Python implementation passes either a mapping (dirstate) or a flat

      /// iterable (manifest)

      pub enum DirsIterable {

          Dirstate(DirstateVec),

          Manifest(Vec<Vec<u8>>),

      }

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				pub mod dirs_multiset;
				pub mod parsers;

				#[derive(Debug, PartialEq, Copy, Clone)]
				pub struct DirstateParents<'a> {
				pub p1: &'a [u8],
				pub p2: &'a [u8],
				}

				/// The C implementation uses all signed types. This will be an issue
				/// either when 4GB+ source files are commonplace or in 2038, whichever
				/// comes first.
				#[derive(Debug, PartialEq)]
				pub struct DirstateEntry {
				pub state: i8,
				pub mode: i32,
				pub mtime: i32,
				pub size: i32,
				}

				pub type DirstateVec = Vec<(Vec<u8>, DirstateEntry)>;

				#[derive(Debug, PartialEq)]
				pub struct CopyVecEntry<'a> {
				pub path: &'a [u8],
				pub copy_path: &'a [u8],
				}

				pub type CopyVec<'a> = Vec<CopyVecEntry<'a>>;

				/// The Python implementation passes either a mapping (dirstate) or a flat
				/// iterable (manifest)
				pub enum DirsIterable {
				Dirstate(DirstateVec),
				Manifest(Vec<Vec<u8>>),
				}